Systems and methods for controlling computer recorded data based on client messages

ABSTRACT

The present disclosure provides event capture systems having one or more processors coupled to memory. The event capture system can identify a wager corresponding to a live event associated with a client device. The event capture system can identify a broadcast receiver device corresponding to the client device. The event capture system can generate recording instructions for the broadcast receiver device that cause the broadcast receiver device to initiate a recording of a broadcast of the live event. The event capture system can transmit the recording instructions to the broadcast receiver device to cause the broadcast receiver device to schedule a recording for the broadcast of the live event.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of and priority to U.S.Provisional Patent Application No. 63/273,580, filed Oct. 29, 2021, andtitled “SYSTEMS AND METHODS FOR IMPROVED MANAGEMENT OF PROCESSINGBROADCAST DATA,” the contents of which is incorporated herein byreference in its entirety for all purposes.

BACKGROUND

Broadcast devices, such as cable boxes or set-top boxes, are used todisplay broadcast content received from a broadcast source. Due to theone-to-many nature of broadcast content, it is challenging to monitorand display information relating to a specific broadcast device withbroadcast content.

SUMMARY

In addition, broadcast receiver devices, such as cable boxes or set topboxes, often include additional functionality that enables recording ofcontent broadcasts. However, conventional systems require manual inputat the broadcast receiver device to schedule a recording of broadcastcontent. This significantly limits the flexibility of broadcastrecording systems. It is therefore advantageous for a system toautomatically record or store records of broadcasts, such as liveevents, based on input from other computing devices. Conventionalbroadcast systems do not communicate with other computing systems thatcapture user input, and thus, cannot record or store broadcastsautomatically that relate to user interests, actions, or onlineactivities. The event capture system described herein can automaticallygenerate recording instructions for broadcast receiver devices to recordbroadcast content based on one or more online activities of a player.Thus, the systems and methods of this technical solution provide atechnical improvement to broadcast capture systems by extending thefunctionality of broadcast receiver devices, namely by, generating andproviding recording instructions based on user input at other computingdevices or systems.

At least one aspect of the present disclosure is directed to an eventcapture system. The event capture system can include one or moreprocessors coupled to memory. The event capture system can identify awager corresponding to a live event associated with a client device. Theevent capture system can identify a broadcast receiver devicecorresponding to the client device. The event capture system cangenerate recording instructions for the broadcast receiver device thatcause the broadcast receiver device to initiate a recording of abroadcast of the live event. The event capture system can transmit therecording instructions to the broadcast receiver device to cause thebroadcast receiver device to schedule a recording for the broadcast ofthe live event.

In some implementations, the event capture system can determine abroadcast schedule of the live event based on information received fromthe broadcast receiver device and generate the recording instructionsfor the broadcast receiver device further based on the broadcastschedule of the live event. In some implementations, the event capturesystem can determine a broadcast schedule of the live event based oninformation received from a third-party data source and generate therecording instructions for the broadcast receiver device further basedon the broadcast schedule of the live event. In some implementations,the event capture system can be further configured to maintain a datastructure storing an association between an identifier of the wager, anidentifier of the client device, and an identifier of the broadcastreceiver device corresponding to the client device. In someimplementations, the event capture system can receive, from the clientdevice, a request to record live events corresponding to wagersassociated with the client device and generate the recordinginstructions responsive to the request to record live eventscorresponding to wagers associated with the client device.

In some implementations, the request to record live events correspondingto wagers is included in the wager corresponding to the live eventassociated with the client device. In some implementations, the eventcapture system can determine that the wager corresponds to a portion ofthe live event and generate the recording instructions to initiate arecording of only the portion of the live event corresponding to thewager. In some implementations, to identify the broadcast receiverdevice corresponding to the client device, the event capture system arefurther configured to identify, from a user profile used by the clientdevice to communicate with the one or more processors, an identifier ofthe broadcast receiver device corresponding to the client device.

In some implementations, to generate the recording instructions for thebroadcast receiver device, the event capture system can be furtherconfigured to generate a notification for display by the broadcastreceiver device that indicates the recording of the broadcast of thelive event has been scheduled. In some implementations, the eventcapture system can determine that the broadcast receiver device isauthorized to record the broadcast of the live event and generate therecording instructions responsive to determining that the broadcastreceiver device is authorized to record the broadcast of the live event.

Various implementations relate to a method, the method implemented byone or more processors coupled to memory. The method includesidentifying a wager corresponding to a live event associated with aclient device. The method further includes identifying a broadcastreceiver device corresponding to the client device. The method furtherincludes generating recording instructions for the broadcast receiverdevice that cause the broadcast receiver device to initiate a recordingof a broadcast of the live event. The method further includestransmitting the recording instructions to the broadcast receiver deviceto cause the broadcast receiver device to schedule a recording for thebroadcast of the live event.

In some implementations, the further includes determining, by the one ormore processors, a broadcast schedule of the live event based oninformation received from the broadcast receiver device and whereingenerating the recording instructions for the broadcast receiver deviceis further based on the broadcast schedule of the live event. In someimplementations, the further includes determining a broadcast scheduleof the live event based on information received from a third-party datasource and wherein generating the recording instructions for thebroadcast receiver device is further based on the broadcast schedule ofthe live event. In some implementations, the further includesmaintaining, by the one or more processors, a data structure storing anassociation between an identifier of the wager, an identifier of theclient device, and an identifier of the broadcast receiver devicecorresponding to the client device. In some implementations, the furtherincludes receiving, by the one or more processors, from the clientdevice, a request to record live events corresponding to wagersassociated with the client device and wherein generating the recordinginstructions is responsive to the request to record live eventscorresponding to wagers associated with the client device.

In some implementations, the request to record live events correspondingto wagers is included in the wager corresponding to the live eventassociated with the client device. In some implementations, the furtherincludes determining, by the one or more processors, that the wagercorresponds to a portion of the live event and generating, by the one ormore processors, the recording instructions to initiate a recording ofonly the portion of the live event corresponding to the wager. In someimplementations, identifying the broadcast receiver device correspondingto the client device further includes identifying from a user profileused by the client device to communicate with the one or moreprocessors, an identifier of the broadcast receiver device correspondingto the client device.

In some implementations, generating the recording instructions for thebroadcast receiver device further includes generating a notification fordisplay by the broadcast receiver device that indicates the recording ofthe broadcast of the live event has been scheduled. In someimplementations, the further includes determining, by the one or moreprocessors, that the broadcast receiver device is authorized to recordthe broadcast of the live event and generating, by the one or moreprocessors, the recording instructions responsive to determining thatthe broadcast receiver device is authorized to record the broadcast ofthe live event.

These and other aspects and implementations are discussed in detailbelow. The foregoing information and the following detailed descriptioninclude illustrative examples of various aspects and implementations,and provide an overview or framework for understanding the nature andcharacter of the claimed aspects and implementations. The drawingsprovide illustration and a further understanding of the various aspectsand implementations, and are incorporated in and constitute a part ofthis specification. Aspects can be combined and it will be readilyappreciated that features described in the context of one aspect of theinvention can be combined with other aspects. Aspects can be implementedin any convenient form. For example, by appropriate computer programs,which may be carried on appropriate carrier media (computer readablemedia), which may be tangible carrier media (e.g. disks) or intangiblecarrier media (e.g. communications signals). Aspects may also beimplemented using suitable apparatus, which may take the form ofprogrammable computers running computer programs arranged to implementthe aspect. As used in the specification and in the claims, the singularform of ‘a’, ‘an’, and ‘the’ include plural referents unless the contextclearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are not intended to be drawn to scale. Likereference numbers and designations in the various drawings indicate likeelements. For purposes of clarity, not every component may be labeled inevery drawing. In the drawings:

FIG. 1A is a block diagram depicting an embodiment of a networkenvironment comprising a client device in communication with a serverdevice;

FIG. 1B is a block diagram depicting a cloud computing environmentcomprising a client device in communication with cloud serviceproviders;

FIGS. 1C and 1D are block diagrams depicting embodiments of computingdevices useful in connection with the methods and systems describedherein;

FIG. 2 is a block diagram of an example event capture system, inaccordance with one or more implementations;

FIGS. 3A and 3B illustrate example live event broadcasts displayed on abroadcast receiver device depicted in FIG. 2 , in accordance with one ormore implementations; and

FIG. 4 illustrates an example flow diagram of a method for providingevent capture system functionalities, in accordance with one or moreimplementations.

DETAILED DESCRIPTION

Below are detailed descriptions of various concepts related to, andimplementations of, techniques, approaches, methods, apparatuses, andsystems for extracting parameters from invoices using a cloud computingsystem. The various concepts introduced above and discussed in greaterdetail below may be implemented in any of numerous ways, as thedescribed concepts are not limited to any particular manner ofimplementation. Examples of specific implementations and applicationsare provided primarily for illustrative purposes.

For purposes of reading the description of the various implementationsbelow, the following descriptions of the sections of the Specificationand their respective contents may be helpful:

Section A describes a network environment and computing environmentwhich may be useful for practicing embodiments described herein; and

Section B describes systems and methods for event capture systems.

A. Computing and Network Environment

Prior to discussing specific implements of the various aspects of thistechnical solution, it may be helpful to describe aspects of theoperating environment as well as associated system components (e.g.,hardware elements) in connection with the methods and systems describedherein. Referring to FIG. 1A, an embodiment of a network environment isdepicted. In brief overview, the network environment includes one ormore clients 102 a-102 n (also generally referred to as local machine(s)102, client(s) 102, client node(s) 102, client machine(s) 102, clientcomputer(s) 102, client device(s) 102, endpoint(s) 102, or endpointnode(s) 102) in communication with one or more agents 103 a-103 n andone or more servers 106 a-106 n (also generally referred to as server(s)106, node 106, or remote machine(s) 106) via one or more networks 104.In some embodiments, a client 102 has the capacity to function as both aclient node seeking access to resources provided by a server and as aserver providing access to hosted resources for other clients 102 a-102n.

Although FIG. 1A shows a network 104 between the clients 102 and theservers 106, the clients 102 and the servers 106 may be on the samenetwork 104. In some embodiments, there are multiple networks 104between the clients 102 and the servers 106. In one of theseembodiments, a network 104′ (not shown) may be a private network and anetwork 104 may be a public network. In another of these embodiments, anetwork 104 may be a private network and a network 104′ a publicnetwork. In still another of these embodiments, networks 104 and 104′may both be private networks.

The network 104 may be connected via wired or wireless links. Wiredlinks may include Digital Subscriber Line (DSL), coaxial cable lines, oroptical fiber lines. The wireless links may include BLUETOOTH, Wi-Fi,Worldwide Interoperability for Microwave Access (WiMAX), an infraredchannel or satellite band. The wireless links may also include anycellular network standards used to communicate among mobile devices,including standards that qualify as 1G, 2G, 3G, or 4G. The networkstandards may qualify as one or more generation of mobiletelecommunication standards by fulfilling a specification or standardssuch as the specifications maintained by International TelecommunicationUnion. The 3G standards, for example, may correspond to theInternational Mobile Telecommunications-2000 (IMT-2000) specification,and the 4G standards may correspond to the International MobileTelecommunications Advanced (IMT-Advanced) specification. Examples ofcellular network standards include AMPS, GSM, GPRS, UMTS, LTE, LTEAdvanced, Mobile WiMAX, and WiMAX-Advanced. Cellular network standardsmay use various channel access methods e.g. FDMA, TDMA, CDMA, or SDMA.In some embodiments, different types of data may be transmitted viadifferent links and standards. In other embodiments, the same types ofdata may be transmitted via different links and standards.

The network 104 may be any type and/or form of network. The geographicalscope of the network 104 may vary widely and the network 104 can be abody area network (BAN), a personal area network (PAN), a local-areanetwork (LAN), e.g. Intranet, a metropolitan area network (MAN), a widearea network (WAN), or the Internet. The topology of the network 104 maybe of any form and may include, e.g., any of the following:point-to-point, bus, star, ring, mesh, or tree. The network 104 may bean overlay network which is virtual and sits on top of one or morelayers of other networks 104′. The network 104 may be of any suchnetwork topology as known to those ordinarily skilled in the art capableof supporting the operations described herein. The network 104 mayutilize different techniques and layers or stacks of protocols,including, e.g., the Ethernet protocol, the internet protocol suite(TCP/IP), the ATM (Asynchronous Transfer Mode) technique, the SONET(Synchronous Optical Networking) protocol, or the SDH (SynchronousDigital Hierarchy) protocol. The TCP/IP internet protocol suite mayinclude application layer, transport layer, internet layer (including,e.g., IPv6), or the link layer. The network 104 may be a type of abroadcast network, a telecommunications network, a data communicationnetwork, or a computer network.

In some embodiments, the system may include multiple, logically-groupedservers 106. In one of these embodiments, the logical group of serversmay be referred to as a server farm 38 (not shown) or a machine farm 38.In another of these embodiments, the servers 106 may be geographicallydispersed. In other embodiments, a machine farm 38 may be administeredas a single entity. In still other embodiments, the machine farm 38includes one or more machine farms 38. The servers 106 within eachmachine farm 38 can be heterogeneous—one or more of the servers 106 ormachines 106 can operate according to one type of operating systemplatform (e.g., WINDOWS NT, manufactured by Microsoft Corp. of Redmond,Wash.), while one or more of the other servers 106 can operate onaccording to another type of operating system platform (e.g., Unix,Linux, or Mac OS X).

In one embodiment, servers 106 in the machine farm 38 may be stored inhigh-density rack systems, along with associated storage systems, andlocated in an enterprise data center. In this embodiment, consolidatingthe servers 106 in this way may improve system manageability, datasecurity, the physical security of the system, and system performance bylocating servers 106 and high performance storage systems on localizedhigh performance networks. Centralizing the servers 106 and storagesystems and coupling them with advanced system management tools allowsmore efficient use of server resources.

The servers 106 of each machine farm 38 do not need to be physicallyproximate to another server 106 in the same machine farm 38. Thus, thegroup of servers 106 logically grouped as a machine farm 38 may beinterconnected using a wide-area network (WAN) connection or ametropolitan-area network (MAN) connection. For example, a machine farm38 may include servers 106 physically located in different continents ordifferent regions of a continent, country, state, city, campus, or room.Data transmission speeds between servers 106 in the machine farm 38 canbe increased if the servers 106 are connected using a local-area network(LAN) connection or some form of direct connection. Additionally, aheterogeneous machine farm 38 may include one or more servers 106operating according to a type of operating system, while one or moreother servers 106 execute one or more types of hypervisors rather thanoperating systems. In these embodiments, hypervisors may be used toemulate virtual hardware, partition physical hardware, virtualizephysical hardware, and execute virtual machines that provide access tocomputing environments, allowing multiple operating systems to runconcurrently on a host computer. Native hypervisors may run directly onthe host computer. Hypervisors may include VMware ESX/ESXi, manufacturedby VMWare, Inc., of Palo Alto, Calif.; the Xen hypervisor, an opensource product whose development is overseen by Citrix Systems, Inc.;the HYPER-V hypervisors provided by Microsoft or others. Hostedhypervisors may run within an operating system on a second softwarelevel. Examples of hosted hypervisors may include VMware Workstation andVIRTUALBOX.

Management of the machine farm 38 may be de-centralized. For example,one or more servers 106 may comprise components, subsystems and modulesto support one or more management services for the machine farm 38. Inone of these embodiments, one or more servers 106 provide functionalityfor management of dynamic data, including techniques for handlingfailover, data replication, and increasing the robustness of the machinefarm 38. Each server 106 may communicate with a persistent store and, insome embodiments, with a dynamic store.

Server 106 may be a file server, application server, web server, proxyserver, appliance, network appliance, gateway, gateway server,virtualization server, deployment server, SSL VPN server, or firewall.In one embodiment, the server 106 may be referred to as a remote machineor a node. In another embodiment, one or more nodes 290 may be in thepath between any two communicating servers.

Referring to FIG. 1B, a cloud computing environment is depicted. A cloudcomputing environment may provide client 102 with one or more resourcesprovided by a network environment. The cloud computing environment mayinclude one or more clients 102 a-102 n, in communication withrespective agents 103 a-103 n and with the cloud 108 over one or morenetworks 104. Clients 102 may include, e.g., thick clients, thinclients, and zero clients. A thick client may provide at least somefunctionality even when disconnected from the cloud 108 or servers 106.A thin client or a zero client may depend on the connection to the cloud108 or server 106 to provide functionality. A zero client may depend onthe cloud 108 or other networks 104 or servers 106 to retrieve operatingsystem data for the client device. The cloud 108 may include back endplatforms, e.g., servers 106, storage, server farms or data centers.

The cloud 108 may be public, private, or hybrid. Public clouds mayinclude public servers 106 that are maintained by third parties to theclients 102 or the owners of the clients. The servers 106 may be locatedoff-site in remote geographical locations as disclosed above orotherwise. Public clouds may be connected to the servers 106 over apublic network. Private clouds may include private servers 106 that arephysically maintained by clients 102 or owners of clients. Privateclouds may be connected to the servers 106 over a private network 104.Hybrid clouds 108 may include both the private and public networks 104and servers 106.

The cloud 108 may also include a cloud based delivery, e.g. Software asa Service (SaaS) 110, Platform as a Service (PaaS) 112, andInfrastructure as a Service (IaaS) 114. IaaS may refer to a user rentingthe use of infrastructure resources that are needed during a specifiedtime period. IaaS providers may offer storage, networking, servers orvirtualization resources from large pools, allowing the users to quicklyscale up by accessing more resources as needed. Examples of IaaS includeAMAZON WEB SERVICES provided by Amazon.com, Inc., of Seattle, Wash.,RACKSPACE CLOUD provided by Rackspace US, Inc., of San Antonio, Tex.,Google Compute Engine provided by Google Inc. of Mountain View, Calif.,or RIGHTSCALE provided by RightScale, Inc., of Santa Barbara, Calif.PaaS providers may offer functionality provided by IaaS, including,e.g., storage, networking, servers or virtualization, as well asadditional resources such as, e.g., the operating system, middleware, orruntime resources. Examples of PaaS include WINDOWS AZURE provided byMicrosoft Corporation of Redmond, Wash., Google App Engine provided byGoogle Inc., and HEROKU provided by Heroku, Inc. of San Francisco,Calif. SaaS providers may offer the resources that PaaS provides,including storage, networking, servers, virtualization, operatingsystem, middleware, or runtime resources. In some embodiments, SaaSproviders may offer additional resources including, e.g., data andapplication resources. Examples of SaaS include GOOGLE APPS provided byGoogle Inc., SALESFORCE provided by Salesforce.com Inc. of SanFrancisco, Calif., or OFFICE 365 provided by Microsoft Corporation.Examples of SaaS may also include data storage providers, e.g. DROPBOXprovided by Dropbox, Inc. of San Francisco, Calif., Microsoft SKYDRIVEprovided by Microsoft Corporation, Google Drive provided by Google Inc.,or Apple ICLOUD provided by Apple Inc. of Cupertino, Calif.

Clients 102 may access IaaS resources with one or more IaaS standards,including, e.g., Amazon Elastic Compute Cloud (EC2), Open CloudComputing Interface (OCCI), Cloud Infrastructure Management Interface(CIMI), or OpenStack standards. Some IaaS standards may allow clientsaccess to resources over HTTP, and may use Representational StateTransfer (REST) protocol or Simple Object Access Protocol (SOAP).Clients 102 may access PaaS resources with different PaaS interfaces.Some PaaS interfaces use HTTP packages, standard Java APIs, JavaMailAPI, Java Data Objects (JDO), Java Persistence API (JPA), Python APIs,web integration APIs for different programming languages including,e.g., Rack for Ruby, WSGI for Python, or PSGI for Perl, or other APIsthat may be built on REST, HTTP, XML, or other protocols. Clients 102may access SaaS resources through the use of web-based user interfaces,provided by a web browser (e.g. GOOGLE CHROME, Microsoft INTERNETEXPLORER, or Mozilla Firefox provided by Mozilla Foundation of MountainView, Calif.). Clients 102 may also access SaaS resources throughsmartphone or tablet applications, including, e.g., Salesforce SalesCloud, or Google Drive app. Clients 102 may also access SaaS resourcesthrough the client operating system, including, e.g., Windows filesystem for DROPBOX.

In some embodiments, access to IaaS, PaaS, or SaaS resources may beauthenticated. For example, a server or authentication server mayauthenticate a user via security certificates, HTTPS, or API keys. APIkeys may include various encryption standards such as, e.g., AdvancedEncryption Standard (AES). Data resources may be sent over TransportLayer Security (TLS) or Secure Sockets Layer (SSL).

The client 102 and server 106 may be deployed as and/or executed on anytype and form of computing device, e.g. a computer, network device orappliance capable of communicating on any type and form of network andperforming the operations described herein. FIGS. 1C and 1D depict blockdiagrams of a computing device 100 useful for practicing an embodimentof the client 102 or a server 106. As shown in FIGS. 1C and 1D, eachcomputing device 100 includes a central processing unit 121, and a mainmemory unit 122. As shown in FIG. 1C, a computing device 100 may includea storage device 128, an installation device 116, a network interface118, an I/O controller 123, display devices 124 a-124 n, a keyboard 126and a pointing device 127, e.g. a mouse. The storage device 128 mayinclude, without limitation, an operating system, software, andbroadcast platform 120, which can implement any of the features of theevent capture system 205 described herein below in conjunction with FIG.2 . As shown in FIG. 1D, each computing device 100 may also includeadditional optional elements, e.g. a memory port 132, a bridge 170, oneor more input/output devices 130 a-130 n (generally referred to usingreference numeral 130), and a cache memory 140 in communication with thecentral processing unit 121.

The central processing unit 121 is any logic circuitry that responds toand processes instructions fetched from the main memory unit 122. Inmany embodiments, the central processing unit 121 is provided by amicroprocessor unit, e.g.: those manufactured by Intel Corporation ofMountain View, Calif.; those manufactured by Motorola Corporation ofSchaumburg, Ill.; the ARM processor and TEGRA system on a chip (SoC)manufactured by Nvidia of Santa Clara, Calif.; the POWER7 processor,those manufactured by International Business Machines of White Plains,N.Y.; or those manufactured by Advanced Micro Devices of Sunnyvale,Calif. The computing device 100 may be based on any of these processors,or any other processor capable of operating as described herein. Thecentral processing unit 121 may utilize instruction level parallelism,thread level parallelism, different levels of cache, and multi-coreprocessors. A multi-core processor may include two or more processingunits on a single computing component. Examples of a multi-coreprocessors include the AMD PHENOM IIX2, INTEL CORE i5, INTEL CORE i7,and INTEL CORE i9.

Main memory unit 122 may include one or more memory chips capable ofstoring data and allowing any storage location to be directly accessedby the microprocessor 121. Main memory unit 122 may be volatile andfaster than storage 128 memory. Main memory units 122 may be Dynamicrandom access memory (DRAM) or any variants, including static randomaccess memory (SRAM), Burst SRAM or SynchBurst SRAM (B SRAM), Fast PageMode DRAM (FPM DRAM), Enhanced DRAM (EDRAM), Extended Data Output RAM(EDO RAM), Extended Data Output DRAM (EDO DRAM), Burst Extended DataOutput DRAM (BEDO DRAM), Single Data Rate Synchronous DRAM (SDR SDRAM),Double Data Rate SDRAM (DDR SDRAM), Direct Rambus DRAM (DRDRAM), orExtreme Data Rate DRAM (XDR DRAM). In some embodiments, the main memory122 or the storage 128 may be non-volatile; e.g., non-volatile readaccess memory (NVRAM), flash memory non-volatile static RAM (nvSRAM),Ferroelectric RAM (FeRAM), Magnetoresistive RAM (MRAM), Phase-changememory (PRAM), conductive-bridging RAM (CBRAM),Silicon-Oxide-Nitride-Oxide-Silicon (SONOS), Resistive RAM (RRAM),Racetrack, Nano-RAM (NRAM), or Millipede memory. The main memory 122 maybe based on any of the above described memory chips, or any otheravailable memory chips capable of operating as described herein. In theembodiment shown in FIG. 1C, the processor 121 communicates with mainmemory 122 via a system bus 150 (described in more detail below). FIG.1D depicts an embodiment of a computing device 100 in which theprocessor communicates directly with main memory 122 via a memory port132. For example, in FIG. 1D the main memory 122 may be DRDRAM.

FIG. 1D depicts an embodiment in which the main processor 121communicates directly with cache memory 140 via a secondary bus,sometimes referred to as a backside bus. In other embodiments, the mainprocessor 121 communicates with cache memory 140 using the system bus150. Cache memory 140 typically has a faster response time than mainmemory 122 and is typically provided by SRAM, BSRAM, or EDRAM. In theembodiment shown in FIG. 1D, the processor 121 communicates with variousI/O devices 130 via a local system bus 150. Various buses may be used toconnect the central processing unit 121 to any of the I/O devices 130,including a PCI bus, a PCI-X bus, or a PCI-Express bus, or a NuBus. Forembodiments in which the I/O device is a video display 124, theprocessor 121 may use an Advanced Graphics Port (AGP) to communicatewith the display 124 or the I/O controller 123 for the display 124. FIG.1D depicts an embodiment of a computer 100 in which the main processor121 communicates directly with I/O device 130 b or other processors 121′via HYPERTRANSPORT, RAPIDIO, or INFINIBAND communications technology.FIG. 1D also depicts an embodiment in which local busses and directcommunication are mixed: the processor 121 communicates with I/O device130 a using a local interconnect bus while communicating with I/O device130 b directly.

A wide variety of I/O devices 130 a-130 n may be present in thecomputing device 100. Input devices may include keyboards, mice,trackpads, trackballs, touchpads, touch mice, multi-touch touchpads andtouch mice, microphones, multi-array microphones, drawing tablets,cameras, single-lens reflex camera (SLR), digital SLR (DSLR), CMOSsensors, accelerometers, infrared optical sensors, pressure sensors,magnetometer sensors, angular rate sensors, depth sensors, proximitysensors, ambient light sensors, gyroscopic sensors, or other sensors.Output devices may include video displays, graphical displays, speakers,headphones, inkjet printers, laser printers, and 3D printers.

Devices 130 a-130 n may include a combination of multiple input oroutput devices, including, e.g., Microsoft KINECT, Nintendo Wiimote forthe WII, Nintendo WII U GAMEPAD, or Apple IPHONE. Some devices 130 a-130n allow gesture recognition inputs through combining some of the inputsand outputs. Some devices 130 a-130 n provides for facial recognitionwhich may be utilized as an input for different purposes includingauthentication and other commands. Some devices 130 a-130 n provides forvoice recognition and inputs, including, e.g., Microsoft KINECT, SIRIfor IPHONE by Apple, Google Now or Google Voice Search.

Additional devices 130 a-130 n have both input and output capabilities,including, e.g., haptic feedback devices, touchscreen displays, ormulti-touch displays. Touchscreen, multi-touch displays, touchpads,touch mice, or other touch sensing devices may use differenttechnologies to sense touch, including, e.g., capacitive, surfacecapacitive, projected capacitive touch (PCT), in-cell capacitive,resistive, infrared, waveguide, dispersive signal touch (DST), in-celloptical, surface acoustic wave (SAW), bending wave touch (BWT), orforce-based sensing technologies. Some multi-touch devices may allow twoor more contact points with the surface, allowing advanced functionalityincluding, e.g., pinch, spread, rotate, scroll, or other gestures. Sometouchscreen devices, including, e.g., Microsoft PIXELSENSE orMulti-Touch Collaboration Wall, may have larger surfaces, such as on atable-top or on a wall, and may also interact with other electronicdevices. Some I/O devices 130 a-130 n, display devices 124 a-124 n orgroup of devices may be augment reality devices. The I/O devices may becontrolled by an I/O controller 123 as shown in FIG. 1C. The I/Ocontroller may control one or more I/O devices, such as, e.g., akeyboard 126 and a pointing device 127, e.g., a mouse or optical pen.Furthermore, an I/O device may also provide storage and/or aninstallation medium 116 for the computing device 100. In still otherembodiments, the computing device 100 may provide USB connections (notshown) to receive handheld USB storage devices. In further embodiments,an I/O device 130 may be a bridge between the system bus 150 and anexternal communication bus, e.g. a USB bus, a SCSI bus, a FireWire bus,an Ethernet bus, a Gigabit Ethernet bus, a Fibre Channel bus, or aThunderbolt bus.

In some embodiments, display devices 124 a-124 n may be connected to I/Ocontroller 123. Display devices may include, e.g., liquid crystaldisplays (LCD), thin film transistor LCD (TFT-LCD), blue phase LCD,electronic papers (e-ink) displays, flexile displays, light emittingdiode displays (LED), digital light processing (DLP) displays, liquidcrystal on silicon (LCOS) displays, organic light-emitting diode (OLED)displays, active-matrix organic light-emitting diode (AMOLED) displays,liquid crystal laser displays, time-multiplexed optical shutter (TMOS)displays, or 3D displays. Examples of 3D displays may use, e.g.stereoscopy, polarization filters, active shutters, or autostereoscopic.Display devices 124 a-124 n may also be a head-mounted display (HMD). Insome embodiments, display devices 124 a-124 n or the corresponding I/Ocontrollers 123 may be controlled through or have hardware support forOPENGL or DIRECTX API or other graphics libraries.

In some embodiments, the computing device 100 may include or connect tomultiple display devices 124 a-124 n, which each may be of the same ordifferent type and/or form. As such, any of the I/O devices 130 a-130 nand/or the I/O controller 123 may include any type and/or form ofsuitable hardware, software, or combination of hardware and software tosupport, enable or provide for the connection and use of multipledisplay devices 124 a-124 n by the computing device 100. For example,the computing device 100 may include any type and/or form of videoadapter, video card, driver, and/or library to interface, communicate,connect or otherwise use the display devices 124 a-124 n. In oneembodiment, a video adapter may include multiple connectors to interfaceto multiple display devices 124 a-124 n. In other embodiments, thecomputing device 100 may include multiple video adapters, with eachvideo adapter connected to one or more of the display devices 124 a-124n. In some embodiments, any portion of the operating system of thecomputing device 100 may be configured for using multiple displays 124a-124 n. In other embodiments, one or more of the display devices 124a-124 n may be provided by one or more other computing devices 100 a or100 b connected to the computing device 100, via the network 104. Insome embodiments software may be designed and constructed to use anothercomputer's display device as a second display device 124 a for thecomputing device 100. For example, in one embodiment, an Apple iPad mayconnect to a computing device 100 and use the display of the device 100as an additional display screen that may be used as an extended desktop.One ordinarily skilled in the art will recognize and appreciate thevarious ways and embodiments that a computing device 100 may beconfigured to have multiple display devices 124 a-124 n.

Referring again to FIG. 1C, the computing device 100 may comprise astorage device 128 (e.g. one or more hard disk drives or redundantarrays of independent disks) for storing an operating system or otherrelated software, and for storing application software programs such asany program related to the broadcast platform 120. Examples of storagedevice 128 include, e.g., hard disk drive (HDD); optical drive includingCD drive, DVD drive, or BLU-RAY drive; solid-state drive (SSD); USBflash drive; or any other device suitable for storing data. Some storagedevices may include multiple volatile and non-volatile memories,including, e.g., solid state hybrid drives that combine hard disks withsolid state cache. Some storage device 128 may be non-volatile, mutable,or read-only. Some storage device 128 may be internal and connect to thecomputing device 100 via a bus 150. Some storage device 128 may beexternal and connect to the computing device 100 via a I/O device 130that provides an external bus. Some storage device 128 may connect tothe computing device 100 via the network interface 118 over a network104, including, e.g., the Remote Disk for MACBOOK AIR by Apple. Someclient devices 100 may not require a non-volatile storage device 128 andmay be thin clients or zero clients 102. Some storage device 128 mayalso be used as an installation device 116, and may be suitable forinstalling software and programs. Additionally, the operating system andthe software can be run from a bootable medium, for example, a bootableCD, e.g. KNOPPIX, a bootable CD for GNU/Linux that is available as aGNU/Linux distribution from knoppix.net.

Computing device 100 may also install software or application from anapplication distribution platform. Examples of application distributionplatforms include the App Store for iOS provided by Apple, Inc., the MacApp Store provided by Apple, Inc., GOOGLE PLAY for Android OS providedby Google Inc., Chrome Webstore for CHROME OS provided by Google Inc.,and Amazon Appstore for Android OS and KINDLE FIRE provided byAmazon.com, Inc. An application distribution platform may facilitateinstallation of software on a client device 102. An applicationdistribution platform may include a repository of applications on aserver 106 or a cloud 108, which the clients 102 a-102 n may access overa network 104. An application distribution platform may includeapplication developed and provided by various developers. A user of aclient device 102 may select, purchase and/or download an applicationvia the application distribution platform.

Furthermore, the computing device 100 may include a network interface118 to interface to the network 104 through a variety of connectionsincluding, but not limited to, standard telephone lines LAN or WAN links(e.g., 802.11, T1, T3, Gigabit Ethernet, Infiniband), broadbandconnections (e.g., ISDN, Frame Relay, ATM, Gigabit Ethernet,Ethernet-over-SONET, ADSL, VDSL, BPON, GPON, fiber optical includingFiOS), wireless connections, or some combination of any or all of theabove. Connections can be established using a variety of communicationprotocols (e.g., TCP/IP, Ethernet, ARCNET, SONET, SDH, Fiber DistributedData Interface (FDDI), IEEE 802.11a/b/g/n/ac CDMA, GSM, WiMax and directasynchronous connections). In one embodiment, the computing device 100communicates with other computing devices 100′ via any type and/or formof gateway or tunneling protocol e.g. Secure Socket Layer (SSL) orTransport Layer Security (TLS), or the Citrix Gateway Protocolmanufactured by Citrix Systems, Inc. of Ft. Lauderdale, Fla. The networkinterface 118 may comprise a built-in network adapter, network interfacecard, PCMCIA network card, EXPRESSCARD network card, card bus networkadapter, wireless network adapter, USB network adapter, modem or anyother device suitable for interfacing the computing device 100 to anytype of network capable of communication and performing the operationsdescribed herein.

A computing device 100 of the sort depicted in FIGS. 1B and 1C mayoperate under the control of an operating system, which controlsscheduling of tasks and access to system resources. The computing device100 can be running any operating system such as any of the versions ofthe MICROSOFT WINDOWS operating systems, the different releases of theUnix and Linux operating systems, any version of the MAC OS forMacintosh computers, any embedded operating system, any real-timeoperating system, any open source operating system, any proprietaryoperating system, any operating systems for mobile computing devices, orany other operating system capable of running on the computing deviceand performing the operations described herein. Typical operatingsystems include, but are not limited to: WINDOWS 2000, WINDOWS Server2012, WINDOWS CE, WINDOWS Phone, WINDOWS XP, WINDOWS VISTA, and WINDOWS7, WINDOWS RT, and WINDOWS 8 all of which are manufactured by MicrosoftCorporation of Redmond, Wash.; MAC OS and iOS, manufactured by Apple,Inc. of Cupertino, Calif.; and Linux, a freely-available operatingsystem, e.g. Linux Mint distribution (“distro”) or Ubuntu, distributedby Canonical Ltd. of London, United Kingdom; or Unix or other Unix-likederivative operating systems; and Android, designed by Google, ofMountain View, Calif., among others. Some operating systems, including,e.g., the CHROME OS by Google, may be used on zero clients or thinclients, including, e.g., CHROMEBOOKS.

The computer system 100 can be any workstation, telephone, desktopcomputer, laptop or notebook computer, netbook, ULTRABOOK, tablet,server, handheld computer, mobile telephone, smartphone or otherportable telecommunications device, media playing device, an eventcapture system, mobile computing device, or any other type and/or formof computing, telecommunications or media device that is capable ofcommunication. The computer system 100 has sufficient processor powerand memory capacity to perform the operations described herein. In someembodiments, the computing device 100 may have different processors,operating systems, and input devices consistent with the device. TheSamsung GALAXY smartphones, e.g., operate under the control of Androidoperating system developed by Google, Inc. GALAXY smartphones receiveinput via a touch interface.

In some embodiments, the computing device 100 is an event capturesystem. For example, the computer system 100 may comprise a PLAYSTATION3, a PLAYSTATION 4, PLAYSTATION 5, or PERSONAL PLAYSTATION PORTABLE(PSP), or a PLAYSTATION VITA device manufactured by the Sony Corporationof Tokyo, Japan, a NINTENDO DS, NINTENDO 3DS, NINTENDO WII, NINTENDO WIIU, or a NINTENDO SWITCH device manufactured by Nintendo Co., Ltd., ofKyoto, Japan, an XBOX 360, an XBOX ONE, an XBOX ONE S, or an XBOX ONE Sdevice manufactured by the Microsoft Corporation of Redmond, Wash.

In some embodiments, the computing device 100 is a digital audio playersuch as the Apple IPOD, IPOD Touch, and IPOD NANO lines of devices,manufactured by Apple Computer of Cupertino, Calif. Some digital audioplayers may have other functionality, including, e.g., an event capturesystem or any functionality made available by an application from adigital application distribution platform. For example, the IPOD Touchmay access the Apple App Store. In some embodiments, the computingdevice 100 is a portable media player or digital audio player supportingfile formats including, but not limited to, MP3, WAV, M4A/AAC, WMAProtected AAC, AIFF, Audible audiobook, Apple Lossless audio fileformats and .mov, .m4v, and .mp4 MPEG-4 (H.264/MPEG-4 AVC) video fileformats.

In some embodiments, the computing device 100 is a tablet e.g. the IPADline of devices by Apple; GALAXY TAB family of devices by Samsung; orKINDLE FIRE, by Amazon.com, Inc. of Seattle, Wash. In other embodiments,the computing device 100 is an eBook reader, e.g. the KINDLE family ofdevices by Amazon.com, or NOOK family of devices by Barnes & Noble, Inc.of New York City, N.Y.

In some embodiments, the communications device 102 includes acombination of devices, e.g. a smartphone combined with a digital audioplayer or portable media player. For example, one of these embodimentsis a smartphone, e.g. the IPHONE family of smartphones manufactured byApple, Inc.; a Samsung GALAXY family of smartphones manufactured bySamsung, Inc.; or a Motorola DROID family of smartphones. In yet anotherembodiment, the communications device 102 is a laptop or desktopcomputer equipped with a web browser and a microphone and speakersystem, e.g. a telephony headset. In these embodiments, thecommunications devices 102 are web-enabled and can receive and initiatephone calls. In some embodiments, a laptop or desktop computer is alsoequipped with a webcam or other video capture device that enables videochat and video call.

In some embodiments, the status of one or more machines 102, 106 in thenetwork 104 is monitored, generally as part of network management. Inone of these embodiments, the status of a machine may include anidentification of load information (e.g., the number of processes on themachine, CPU and memory utilization), of port information (e.g., thenumber of available communication ports and the port addresses), or ofsession status (e.g., the duration and type of processes, and whether aprocess is active or idle). In another of these embodiments, thisinformation may be identified by one or more metrics, and the pluralityof metrics can be applied at least in part towards decisions in loaddistribution, network traffic management, and network failure recoveryas well as any aspects of operations of the present solution describedherein. Aspects of the operating environments and components describedabove will become apparent in the context of the systems and methodsdisclosed herein.

B. Event Capture Systems with Recording Instruction Generation

Conventionally, broadcast receiver systems or devices, such as cableboxes, set top boxes, and satellite receiver boxes, operate using fixedhardware and software that does not enable third-party communicationswith external sources. For example, although cable boxes may communicatewith broadcast provider systems, such as cable providers or otherbroadcast providers, such receiver boxes are generally unable to displayadditional content or monitor the broadcast content displayed bybroadcast provider systems. Further, even if such broadcast receiverdevices include applications that can communicate with third-partyservers, these devices do not include the capabilities to displaycontent or application information at the same time (e.g., in a seamlessmanner) as broadcast content provided by broadcast systems. The systemsand methods of this technical solution these and other issues byextending the functionality of applications and environments onbroadcast receiver devices, to provide applications that displayadditional content, which may include notifications, alerts, or otherinteractive interfaces, with broadcast content. To do so, a server orother external computing device can generate display instructions forapplications executing on such broadcast receiver devices to displayadditional user interfaces with broadcast content, and transmit thoseinstructions via a computer network or via a proprietary broadcastnetwork maintained by a broadcast provider. In doing so, the additionalcontent, which may include interactive user interfaces, can be displayedsuch that it that seamlessly integrates the application interfaces withbroadcast content provided by a broadcast provider system.

The systems and methods of this technical solution provide techniquesfor improved event capture systems that generate and provideinstructions to record content broadcasts in response to identifyingcertain online activities. The event capture system described herein canbe implemented, for example, in a cloud computing environment, such asthe cloud computing environment 108 described herein above inconjunction with FIGS. 1A and 1B. In general, event capture systems canprovide recording instructions to broadcast receiver devices that causethe broadcast receiver devices to schedule a recording for broadcasts ofa live events related to online actions performed by a user (e.g., awager, a request to record the live event, etc.). One example of a wageris a straight bet in which a player wagers on a single game or eventthat carries a point-spread or total, and where a player receives apayout if they correctly wager on the team or event that covers thespread. Another example of a wager is a parlay bet in which a playerwagers on two or more games or events (e.g., using money line bets,straight bets, proposition (or prop) bets, teaser bets) together, andwhere a player receives a payout if they correctly wagered on each gameor event. However, it should be understood that other payout schemes arepossible.

The systems and methods described herein improve upon the limitations ofconventional broadcast systems by automatically generating andcommunicating recording instructions to a broadcast receiver devicebased on online actions of a player, such as a wager. In someimplementations, a wager may be placed by a player before the liveevent. In various implementations, a wager may be placed in real-timeduring the live event. Accordingly, upon identifying wagers of playersthe event capture system can generate and provide recording instructionsto broadcast receiver devices associated with the player. It should beunderstood that in some implementations, recording instructions may beprovided without a player interaction or online activity (e.g., wager).

The systems and methods described herein leverage cloud computing andlive event technology to provide recording instructions for live eventsto player devices, such as broadcast receivers, laptops, smart phones,personal computers, smart televisions, or other such computing devices.Although certain aspects of the computing systems described herein arerepresented as taking place over a network, it should be understood thatsimilar operations can take place on an event capture system, such as asportsbook machine, or another type of independent event capture systemsthat may not require communications between an event capture system anda separate live event client and/or broadcast receiver to effectuate theoperations described herein. These and other features of event capturesystem are described in greater detail herein below.

In addition, the term “broadcast” need not necessarily be limited tocontent provided via proprietary television networks (e.g., cable,fiber-optic, satellite, etc.). Indeed, the term “broadcast,” as usedherein, may be used to describe both television content andlive-streaming content provided via computer networks from one or moreservers. Such live streams may be provided to various client devices orbroadcast receiver devices via one or more computer networks. The livestreams may depict live events such as sport games, poker matches,Olympic Games, live reality shows, and live game shows, among others.

Referring now to FIG. 2 , illustrated is a block diagram of an examplesystem 200, in accordance with one or more implementations. The system200 can include at least one event capture system 205, at least onenetwork 210, a broadcast provider system 215, and one or more broadcastreceiver devices 220A-220 (sometimes generally referred to as broadcastreceiver device(s) 220), one or more client devices 225A-225N (sometimesgenerally referred to as client device(s) 225). The event capture system205 can include at least one wager analyzer 230, at least one receiveranalyzer 235, at least one instruction generator 240, at least onecapture communicator 245, and at least one database 250. The database250 can include one or more accounts 255, one or more play information260 data structures (sometimes generally referred to as the playinformation 260), and one or more capture instructions 265 datastructures (sometimes generally referred to as the capture instructions265). In some implementations, the database 250 can be external to theevent capture system 205, for example, as a part of a cloud computingsystem or an external computing device in communication with the devices(e.g., the event capture system 205, the broadcast provider system 215,the broadcaster receiver devices 220, and/or the client devices 225,etc.) of the system 200 via the network 210.

Each of the components (e.g., the event capture system 205, the network210, the broadcast provider system 215, the broadcast receiver device220, the client devices 225, the live event communicator 230, the liveevent monitor 235, the live event analyzer 240, the device determiner245, etc.) of the system 200 can be implemented using the hardwarecomponents or a combination of software with the hardware components ofa computing system, such as the computing system 100 detailed herein inconjunction with FIGS. 1A-1D, or any other computing system describedherein. Each of the components of the event capture system 205 canperform the functionalities detailed herein.

The event capture system 205 can include at least one processor and amemory, e.g., a processing circuit. The memory can storeprocessor-executable instructions that, when executed by processor,cause the processor to perform one or more of the operations describedherein. The processor may include a microprocessor, anapplication-specific integrated circuit (ASIC), a field-programmablegate array (FPGA), etc., or combinations thereof. The memory mayinclude, but is not limited to, electronic, optical, magnetic, or anyother storage or transmission device capable of providing the processorwith program instructions. The memory may further include a floppy disk,CD-ROM, DVD, magnetic disk, memory chip, ASIC, FPGA, read-only memory(ROM), random-access memory (RAM), electrically erasable programmableROM (EEPROM), erasable programmable ROM (EPROM), flash memory, opticalmedia, or any other suitable memory from which the processor can readinstructions. The instructions may include code from any suitablecomputer programming language. The event capture system 205 can includeone or more computing devices or servers that can perform variousfunctions as described herein. The event capture system 205 can includeany or all of the components and perform any or all of the functions ofthe computer system 100 described herein in conjunction with FIGS.1A-1D.

The network 210 can include computer networks such as the Internet,local, wide, metro or other area networks, intranets, satellitenetworks, other computer networks such as voice or data mobile phonecommunication networks, and combinations thereof. The event capturesystem 205 of the system 200 can communicate via the network 210, forinstance with one or more client devices 225. The network 210 may be anyform of computer network that can relay information between the eventcapture system 205, the broadcast provider system 215, the broadcastreceiver devices 220, the one or more client devices 225, and one ormore information sources, such as web servers or external databases,amongst others. In some implementations, the network 210 may include theInternet and/or other types of data networks, such as a local areanetwork (LAN), a wide area network (WAN), a cellular network, asatellite network, or other types of data networks. The network 210 mayalso include any number of computing devices (e.g., computers, servers,routers, network switches, etc.) that are configured to receive and/ortransmit data within the network 210.

The network 210 may further include any number of hardwired and/orwireless connections. Any or all of the computing devices describedherein (e.g., the event capture system 205, the broadcast providersystem 215, the broadcast receiver devices 220, the one or more clientdevices 225, the computer system 100, etc.) may communicate wirelessly(e.g., via WiFi, cellular, radio, etc.) with a transceiver that ishardwired (e.g., via a fiber optic cable, a CAT6 cable, etc.) to othercomputing devices in the network 210. Any or all of the computingdevices described herein (e.g., the event capture system 205, thebroadcast provider system 215, the broadcast receiver devices 220, theone or more client devices 225, the computer system 100, etc.) may alsocommunicate wirelessly with the computing devices of the network 210 viaa proxy device (e.g., a router, network switch, or gateway). In someimplementations, the network 210 can be similar to or can include thenetwork 104 or the cloud 108 described herein above in conjunction withFIGS. 1A and 1B.

The broadcast provider system 215 can include at least one processor anda memory, e.g., a processing circuit. The memory can storeprocessor-executable instructions that, when executed by processor,cause the processor to perform one or more of the operations describedherein. The processor can include a microprocessor, an ASIC, an FPGA,etc., or combinations thereof. The memory can include, but is notlimited to, electronic, optical, magnetic, or any other storage ortransmission device capable of providing the processor with programinstructions. The memory can further include a floppy disk, CD-ROM, DVD,magnetic disk, memory chip, ASIC, FPGA, ROM, RAM, EEPROM, EPROM, flashmemory, optical media, or any other suitable memory from which theprocessor can read instructions. The instructions can include code fromany suitable computer programming language. The broadcast providersystem 215 can include one or more computing devices or servers that canperform various functions as described herein. The broadcast providersystem 215 can include any or all of the components and perform any orall of the functions of the computer system 100 described herein inconjunction with FIGS. 1A-1D. The broadcast provider system 215 caninclude similar features and functionality of client devices 102described herein above in conjunction with FIGS. 1A-1D.

The broadcast provider system 215 can be implemented using hardware or acombination of software and hardware. In some implementations, thebroadcast provider system 215 can be configured to provide cableservices. The cable services can be provided via a cable distributionnetwork or over network 210. A cable distribution network can connectthe distribution source (e.g., broadcast provider system 215) to theequipment of a player (e.g., broadcast receiver devices 220). In someimplementations, the connection can be a hard-wired cable networkutilizing coaxial, twisted-pair, and fiber-optic, among others. Invarious implementations, the connection can be a wireless networkutilizing a mobile network (e.g., 4G, 5G, 6G), and satellites, amongothers.

Additionally, the broadcast provider system 215 can include an inputdevice that couples and communicates with the various computing devicesdescribed herein. For example, the broadcast provider system 215 may beconfigured to relay data received from the broadcast receiver devices220 and/or client devices 225 to event capture system 205. In anotherexample, the broadcast provider system 215 may receive instructions fromthe event capture system 205 and subsequently, communicate with eachbroadcast receiver device 220 of a subset of broadcast receiver devices220 to cause a broadcast receiver device 220 to automatically scheduleand record a live event associated with a wager based on instructions.

Each of the broadcast receiver devices 220 can include at least oneprocessor and a memory, e.g., a processing circuit. The memory can storeprocessor-executable instructions that, when executed by processor,cause the processor to perform one or more of the operations describedherein. The processor can include a microprocessor, anapplication-specific integrated circuit (ASIC), a field-programmablegate array (FPGA), etc., or combinations thereof. The memory caninclude, but is not limited to, electronic, optical, magnetic, or anyother storage or transmission device capable of providing the processorwith program instructions. The memory can further include a floppy disk,CD-ROM, DVD, magnetic disk, memory chip, ASIC, FPGA, read-only memory(ROM), random-access memory (RAM), electrically erasable programmableROM (EEPROM), erasable programmable ROM (EPROM), flash memory, opticalmedia, or any other suitable memory from which the processor can readinstructions. The instructions can include code from any suitablecomputer programming language. The broadcast receiver devices 220 caninclude one or more computing devices or servers that can performvarious functions as described herein. The one or more broadcastreceiver devices 220 can include any or all of the components andperform any or all of the functions of the computer system 100 describedherein in conjunction with FIGS. 1A-1D.

Each of the broadcast receiver devices 220 can include similar featuresand functionality of client devices 102 described herein above inconjunction with FIGS. 1A-1D. Each of the broadcast receiver devices 220can include at least one processor and a memory, e.g., a processingcircuit. The memory can store processor-executable instructions that,when executed by processor, cause the processor to perform one or moreof the operations described herein. The processor can include amicroprocessor, an ASIC, an FPGA, etc., or combinations thereof. Thememory can include, but is not limited to, electronic, optical,magnetic, or any other storage or transmission device capable ofproviding the processor with program instructions. The memory canfurther include a floppy disk, CD-ROM, DVD, magnetic disk, memory chip,ASIC, FPGA, ROM, RAM, EEPROM, EPROM, flash memory, optical media, or anyother suitable memory from which the processor can read instructions.The instructions can include code from any suitable computer programminglanguage. The broadcast receiver devices 220 can include one or morecomputing devices or servers that can perform various functions asdescribed herein. The one or more broadcast receiver devices 220 caninclude any or all of the components and perform any or all of thefunctions of the computer system 100 described herein in conjunctionwith FIGS. 1A-1D. The broadcast receiver devices 220 can include similarfeatures and functionality of client devices 102 described herein abovein conjunction with FIGS. 1A-1D.

Each broadcast receiver device 220 can include, but is not limited to, acable box (cable converter box, or television converter box), a set-topbox, a satellite receiver, a special-use PC Card device (e.g.,CableCard, AllVid), a television device, a mobile device, or anothertype of computing device. A cable box can be a computing deviceconfigured to convert digital television signals to analog (or digital)or unscramble a television signal provided by the broadcast providersystem 215 and/or event capture system 205. A set-top box can be acomputing device that can be configured to enable a television oranother type of computing device to receive and decode device digitaltelevision (DTV) broadcasts. A satellite receiver can be a computingdevice that can be configured to wirelessly (e.g., over network 210)receive and decode radio signals suitable for viewing by a player.Generally, the cable boxes, set-top boxes, and satellite receivers canbe tuning devices that can transpose or convert channels from a cabletelevision service (e.g., provided by broadcast provider system 215 orevent capture system 205) to an analog (or digital) radio frequency (RF)signal. In some implementations, the broadcast receiver device 220 canbe a television or another type of computing device with a converterintegrated within the broadcast receiver device 220 (e.g., within a sameenclosure).

Each broadcast receiver device 220 can be implemented using hardware ora combination of software and hardware. In some implementations, eachbroadcast receiver device 220 can be configured to receive cableservices from the broadcast provider system 215. In variousimplementations, a broadcast receiver device 220 can include a displayor display portion. Alternatively, the broadcast receiver device 220 canbe configured to provide a converted signal for display on a computingdevice such as a client device 225 (e.g., smart phone, etc.). Thedisplay can include a display portion of a television, a display portionof a computing device, a graphical user interface (GUI), or another typeof interactive display (e.g., a remote, a controller, a gamepad, atouchscreen, a display, etc.) and one or more input/output (I/O) devices(e.g., a mouse, a keyboard, digital keypad). The display can include oneor more portions, for example, to display multiple in-game events asdescribed herein. The broadcast receiver device 220 can execute one ormore applications, which may display graphical user interfaces such aslive event windows and/or notification windows with live content, asdescribed herein. The display can include a border region (e.g., sideborder, top border, bottom border). In some implementations, thebroadcast receiver device 220 can receive one or more interactions froma player (e.g., via an input device such as a remote, controller,gamepad, keyboard, or mouse, etc.). The interactions can result ininteraction data, which can be stored and transmitted by the processingcircuitry of the broadcast receiver device 220. The interaction data caninclude, for example, interaction coordinates, an interaction type(e.g., click, swipe, scroll, tap, etc.), and an indication of anactionable object (e.g., an interactive user interface element such as abutton, a hyperlink, etc.) with which the interaction occurred. Eachbroadcast receiver device 220 can include an input device that couplesor communicates with the display of each client device 225 to enable aplayer to interact with and/or select one or more actionable objects asdescribed herein. The application executing on the broadcast receiverdevice 220 can display interactive content with live broadcasts receivedby the broadcast receiver device 220, and be responsive to aninteraction (e.g., select, click-on, touch, hover), the applicationexecuting on the broadcast receiver device 220 can generate anindication identifying a user input and/or selection of a wager, or anin-game event, among others.

In some implementations, the broadcast receiver device 220 can beconfigured to convert digital television signals to analog signalsand/or unscramble a television signal. Upon converting and/orunscrambling the digital television signal, the broadcast receiverdevice 220 can provide an output to the display in communication withbroadcast receiver device 220. For example, the broadcast receiverdevice 220 may be an all-in-one computing device configured to receiveand configure signals (e.g., from the event capture system 205) and canbe configured to display (or stream) content of the television signalson an integrated display of the broadcast receiver device 220. In thefollowing example, the broadcast receiver device 220 may be atelevision, a smart television, and/or an internet enabled device with adisplay, among others. In another example, the broadcast receiver device220 may be a cable box (or set-top box) configured to receive andconfigure signals (e.g., from the broadcast provider system 215) and canbe configured to display (or stream) content of the television signalson an integrated display of the broadcast receiver device 220.

In various implementations, the broadcast receiver device 220 may havememory (or storage) that can be used to store recordings. The recordingscan be of broadcasts (e.g., provided by the broadcast provider system215 and/or event capture system 205) such a live event associated withone or more schedules. The broadcast receiver device 220 can receiverecording instructions from the event capture system 205 (e.g., viabroadcast provider system 215, or directly via network 210) that can beexecuted on the broadcast receiver device 220 to schedule and recordspecific live events, or parts of a live event. For example, thebroadcast receiver device 220 may include, or be in communication with,a digital video recorder (DVR) device, which can record video in adigital format to a non-transitory memory.

In some implementations, the broadcast receiver device 220 may be acomputer-enabled television (referred to herein as a “smart television”)that receives decoded broadcast content via a set top box, cable box, ora computing device that receives broadcast satellite signals (a“satellite box”). In such implementations, the broadcast receiver device220 can receive and display broadcast content provided by the broadcastprovider system 215 via the cable box, set top, or satellite box. Thebroadcast receiver device 220 can execute one or more applications,which may be associated with as the event capture system 205 describedin greater detail herein below. The application executing on thebroadcast receiver device 220 can establish one or more communicationsessions with the event capture system 205 via the network 210. Theapplication(s) can receive instructions to display notifications asdescribed herein from the event capture system 205, which may bepresented on one or more user interfaces with the broadcast contentreceived via the cable box, set top box, or satellite box. In suchimplementations, the broadcast receiver device 220 can communicate withthe cable box, set top box, or satellite box to perform one or moreactions, such as schedule or modify a recording, or to change to adifferent broadcast channel.

For example, in some implementations, the instructions provided by theevent capture system 205 can include instructions to present actionableobjects which, when actuated, cause the broadcast receiver device 220 toschedule a recording for a broadcast of a live event (or a portion ofthe broadcast). In some implementations, the instructions may includeinstructions that cause the broadcast receiver device 220 to schedule arecording for a broadcast of a live event (or a portion of thebroadcast), rather than display a corresponding notification. To do so,the smart television (e.g., the broadcast receiver device 220), maycommunicate a request to the cable box, set top box, or satellite box torecord broadcast content (or a portion of the broadcast content)identified in the instructions. For example, the instructions mayidentify a particular channel or channel(s) on which the broadcastcontent is being displayed, a start time for the recording, an end timefor the recording, or a duration of the recording. The broadcastreceiver device 220 (or the application executing thereon) can send arequest to the DVR, the cable box, set top box, or satellite box tonavigate to schedule a recording at the identified channel for at thestart time for the live event (or the portion thereof).

In some implementations, the application executing on the smarttelevision (e.g., the broadcast receiver device 220) can communicatewith the broadcast provider system 215 to request a channel guide orschedule corresponding to the player associated with the cable box, settop box, or satellite box. Using the channel guide, the applicationexecuting on the broadcast receiver device 220 can identify the specificchannel on which the broadcast content identified in the instructions isbeing provided, as well as the duration of the broadcast (or anidentified portion of the broadcast). Once the channel, start time, andend time are identified, the broadcast receiver device 220 can transmita request to the DVR, cable box, set top box, or satellite box toschedule a recording for the identified broadcast content on theidentified channel at the identified start time (until the identifiedend time, e.g., based on the duration of the recording). The broadcastreceiver device 220 can communicate with the DVR, cable box, set topbox, or satellite box via any number of communication protocols, such asa Bluetooth protocol, a WiFi protocol (e.g., web-sockets), or any othertype of communication protocol. The broadcast receiver device 220 canutilize one or more APIs corresponding to the DVR, cable box, set topbox, or satellite box, that provide functions to schedule or modifyrecordings according to requests.

Each broadcast receiver device 220 can include a device identifier,which can be specific to each respective broadcast receiver device 220.The device identifier can include a script, code, label, or marker thatidentifies a particular broadcast receiver device 220. In someimplementations, the device identifier can include a string or pluralityof numbers, letters, characters or any combination of numbers, letters,and characters. In some embodiments, each broadcast receiver device 220can have a unique device identifier. Each broadcast receiver device 220can include a client application, which can be a live event applicationthat communicates with the event capture system 205 to receive captureinstructions described herein (sometimes referred to herein as“recording instructions”). The client application can include a userapplication executing on each broadcast receiver device 220 or providedto the broadcast receiver device 220 by the server 102. The applicationcan include a web application, a server application, a resource, adesktop, or a file. In some implementations, the application can includea local application (e.g., local to a broadcast receiver device 220),hosted application, Software as a Service (SaaS) application, virtualapplication, mobile application, and other forms of content. In someimplementations, the application can include or correspond toapplications provided by remote servers or third-party servers. In someimplementations, the application can access the accounts 255, the playinformation 260, or the capture instructions 265, stored and maintainedat the database 250, and generate one or more recording instructions,such as a live event recording described herein below in conjunctionwith FIGS. 3A-3B, associated with a wager by a player. Such recordinginstructions can include instructions that cause the broadcast receiverdevice 220 to schedule one or more recordings of broadcast content. Theinstructions may include one or more API calls for recording provided bythe broadcast provider system 215 to access the recording functionalityof the broadcast receiver devices 220. In some implementations, theinstructions can access an API provided by an application executing onthe broadcast receiver devices 220 that interacts with an operatingsystem or software layer of the broadcast provider system 215 to providerecording functionality. In various implementations, the instructionscan be received, for example, by the broadcast provider system 215, andcan include indications or identifiers of the broadcast receiver devices220 to which the instructions should be transmitted.

In some implementations, one or more broadcast receiver devices 220 canestablish one or more communication sessions of the event capture system205, the broadcast provider system 215, and/or the one or more clientdevices 225. The one or more communication sessions can each include achannel or connection between the event capture system 205 and the oneor more broadcast receiver devices 220. The one or more communicationsystems can each include an application session (e.g., virtualapplication), an execution session, a desktop session, a hosted desktopsession, a terminal services session, a browser session, a remotedesktop session, a URL session and/or a remote application session. Eachcommunication session can include encrypted and/or secure sessions,which can include an encrypted file, encrypted data, or traffic. Thecommunication session may be established via the broadcast providersystem 215.

In some implementations, the broadcast provider system 215 can be anintermediary device between the one or more broadcast receiver devices220 and event capture system 205. In particular, a communication sessioncan be established between the broadcast receiver devices 220 and eventcapture system 205 via the broadcast provider system 215. For example,the broadcast provider system 215 can receive data (e.g., wagers,real-time live event information, messages, etc.) from the broadcastreceiver device 220 via a cable distribution network or network 210. Inresponse to receiving data the broadcast provider system 215 can route(or forward) the data to the event capture system 205 via network 210.In some implementations, the broadcast provider system 215 may analyzethe data and modify various data structures such as, but not limited to,removing identifying information, removing secure information, removingfinancial information, adding a broadcast provider system identifier,adding profile and/or use information, etc. prior to routing the data tothe event capture system 205. Furthermore, the broadcast provider systemcan also receive data from the event capture system 205 that can berouted to the broadcast receiver device 220 (using similar techniquesdescribed above). In various implementations, the event capture system205 and broadcast receiver device 220 can establish a directcommunication session via network 210. In some implementations, thecommunication session may be secure such that data can be masked by thebroadcast receiver device 220 and/or broadcast provider system 215 priorto sending it to the event capture system 205.

In implementations where the broadcast receiver devices 220 cancommunicate via the network 210, each of the broadcast receiver devices220 can access information resources, such as web pages via a webbrowser, or application resources via a native application executing ona broadcast receiver device 220. When accessing information resources,the broadcast receiver device 220 can execute instructions (e.g.,embedded in the native applications, in the information resources, etc.)that cause the broadcast receiver devices 220 to display captureinterfaces, such as the capture interfaces described herein below inconjunction with FIGS. 3A-3B. The capturing interfaces can be, forexample, application interfaces that present information regarding oneor more capturing/capture live events. In general, live events includecontent (e.g., images, video, animations, graphics, audio, etc.) thatcan be presented to a player via the input/output interfaces of a clientdevice 225, and/or broadcast receiver device 220. In someimplementations, the broadcast receiver devices 220 may be computingdevices that receive broadcast content in the form of a live-streamvideo, for example, via the internet. Live stream videos of live eventsmay be provided via web-based or native application interfaces, and maybe received by the broadcast receiver devices 220 via one or moresuitable computer networks (e.g., the network 210). In suchimplementations, the broadcast provider system 215 may be a provider oflive stream broadcast content, and can provide the live stream broadcastcontent via the network 210. Similarly, in such implementations, thebroadcast receiver devices 220 may be any type of computing devicecapable of receiving live stream content via a computer network.

In some implementations, player can make wagers on the broadcastreceiver devices 220 and/or client devices 225. In response to a wagerfrom a player, the broadcast receiver device 220 and/or client device225 can transmit information, such as account information (e.g.,changing account parameters, changing login information, etc.),interaction information, selections of wager amounts, selections ofwager participation in live events, or other signals to the eventcapture system 205. In some implementations, the event capture system205 can transmit a recording instructions for one or more live eventbased on the wager. The request can include, for example, a request toschedule a particular live event (e.g., can include a live eventidentifier, etc.) for recording, which can include the wager amount. Therecording instructions can be a hypertext transfer protocol (HTTP orHTTPS) request message, a file transfer protocol message, an emailmessage, a text message, or any other type of message that can betransmitted via the network 210.

In general, upon receiving a wager or an indication of an ongoing wager,an event capture system 205 can identifying a broadcast receiver device220 corresponding to the wager. Capture instructions 265 can include oneor more data structures that include any information related to anevent, such as current time, current score, wager information (e.g.,information about previous wagers, information about ongoing wagers),previous and ongoing recordings, other capture instructions describedherein. In some implementations, the capture instructions 265 can beupdated in real-time on the broadcast receiver device 220 (or clientdevices 225) as the live event occurs (or progresses) (e.g., as theevent is processed by the event capture system 205 according to theevent information 265, etc.). The indications of capture instructions265 can include instructions that cause the broadcast receiver device220 to schedule and/or record a specific live event based on generatedinstructions provided by the event capture system 205. That is, thebroadcast receiver devices 220 can receive instructions from the eventcapture system 205 that can cause the broadcast receiver device 220 toconfigure one or more recordings, such as scheduling a recordingassociated with a television schedule (e.g., television guide,television listing, program listing, etc.). In some implementations, thetelevision schedule may be provided by the broadcast provider system 215and/or event capture system 205.

As described herein, a broadcast receiver device 220 can receive one ormore instructions with objects presented on the display of the clientdevice 225 (as shown with reference to FIG. 3A-3B). In someimplementations, the objects can be interactive (e.g., actionableobjects) that can be tap interactions, click interactions, or othertypes of indications that a user has engaged with a particular userinterface element. Upon detecting an interaction with a particular userinterface element, the broadcast receiver device 220 can executeinstructions (e.g., processor-readable code, a script, etc.) that causethe broadcast receiver device 220 to transmit an appropriate signal tothe event capture system 205, for example, via the broadcast providersystem 215. A signal can include any information specified by theinstructions associated with the particular actionable object with whichthe user interacted. The signals can include, for example, a wager, arequest to stop recording a live event associated with an ongoing wager,a request to delete a recording of a live event associated with aprevious wager, among others.

As described herein, a broadcast receiver device 220 and the eventcapture system 205 can exchange messages directly (or indirectly viabroadcast provider system 215) containing information that causes arecording to be schedule for one or more live events. In someimplementations, the recording instructions can be transmitted inreal-time upon receiving a wager from a player. In variousimplementations, recording instructions can transmitted at set intervals(e.g., every minute, every hour, every day at noon, etc.). In someimplementations, the recording instructions may be packaged togethersuch that one or more recordings can be scheduled by the broadcastreceiver device 220 in response to receiving the recording instructionsfrom the event capture system 205.

The client devices 225 can include similar features and functionalitiesas the broadcast receiver device 220. Each of the client devices 225 caninclude at least one processor and a memory, e.g., a processing circuit.The memory can store processor-executable instructions that, whenexecuted by processor, cause the processor to perform one or more of theoperations described herein. The processor can include a microprocessor,an ASIC, a FPGA, etc., or combinations thereof. The memory can include,but is not limited to, electronic, optical, magnetic, or any otherstorage or transmission device capable of providing the processor withprogram instructions. The memory can further include a floppy disk,CD-ROM, DVD, magnetic disk, memory chip, ASIC, FPGA, ROM, RAM, EEPROM,EPROM, flash memory, optical media, or any other suitable memory fromwhich the processor can read instructions. The instructions can includecode from any suitable computer programming language. The client devices225 can include one or more computing devices or servers that canperform various functions as described herein. The one or more clientdevices 225 can include any or all of the components and perform any orall of the functions of the computer system 100 described herein inconjunction with FIGS. 1A-1D. The client devices 225 can be, or can besimilar to, the client devices 102 described herein above in conjunctionwith FIGS. 1A-1D.

Each client device 225 can include, but is not limited to, a smartphone,a mobile device, a personal computing device, or another type ofcomputing device. Each client device 225 can be implemented usinghardware or a combination of software and hardware. Each client device225 can include a display or display portion. The display can include adisplay portion of a television, a display portion of a computingdevice, a GUI, or another type of interactive display (e.g., atouchscreen, a display, etc.) and one or more I/O devices (e.g., amouse, a keyboard, digital key pad). The display can include one or moreportions, for example, to display in-game events, make wagers, andconfigure captures as described herein. The display can include a touchscreen displaying an application, such as live event windows and/ornotification windows described herein.

The display can include a border region (e.g., side border, top border,bottom border). In some implementations, the display can include a touchscreen display, which can receive interactions from a player. Theinteractions can result in interaction data, which can be stored andtransmitted by the processing circuitry of the client device 225. Theinteraction data can include, for example, interaction coordinates, aninteraction type (e.g., click, swipe, scroll, tap, etc.), and anindication of an actionable object with which the interaction occurred(e.g., wager). Each client device 225 can include an input device thatcouples or communicates with the display of each client device 225 toenable a player to interact with and/or select one or more actionableobjects as described herein. The display can enable interaction with oneor more visual indications provided through the display of each clientdevice 225, and responsive to an interaction (e.g., select, click-on,touch, hover), the client device 225 can generate an indicationidentifying a user input and/or selection of a wager, or an in-gameevent, among others.

Each client device 225 can include a device identifier, which can bespecific to each respective client device 225. The device identifier caninclude a script, code, label, or marker that identifies a particularclient device 225. In some implementations, the device identifier caninclude a string or plurality of numbers, letters, characters or anycombination of numbers, letters, and characters. In some embodiments,each client device 225 can have a unique device identifier. Each clientdevice 225 can include a client application, which can be a wagerapplication and/or live event application that communicates with theevent capture system 205 to view live events, make wagers, and schedulerecordings described herein. The client application can include a userapplication executing on each client device 225 or provided to theclient device 225 by the server 102. The application can include a webapplication, a server application, a resource, a desktop, or a file. Insome implementations, the application can include a local application(e.g., local to a client device 225), hosted application, SaaSapplication, virtual application, mobile application, and other forms ofcontent. In some implementations, the application can include orcorrespond to applications provided by remote servers or third-partyservers. In some implementations, the application can access theaccounts 255, the play information 260, or the capture instructions 265,stored and maintained at the database 250, and generate recordinginstructions, such as notifications and/or instructions to record a liveevent described herein below in conjunction with FIGS. 3A-3B, to a userthrough a client device 225. Such notifications can include actionableobjects that can include user-selectable hyperlinks, buttons, graphics,videos, images, or other application features that generate a signalthat is processed by the application executing on the respective clientdevice 225.

In some implementations, one or more client devices 225 can establishone or more communication sessions between the event capture system 205,the broadcast provider system 215, the broadcast receiver devices 220,and/or the one or more client devices 225. The one or more communicationsessions can each include a channel or connection between the eventcapture system 205 and the one or more client devices 225. The one ormore communication sessions can each include an application session(e.g., virtual application), an execution session, a desktop session, ahosted desktop session, a terminal services session, a browser session,a remote desktop session, a URL session and/or a remote applicationsession. Each communication session can include encrypted and/or securesessions, which can include an encrypted file, encrypted data ortraffic.

Each of the client devices 225 can be computing devices configured tocommunicate via the network 210 to access information resources, such asweb pages via a web browser, or application resources via a nativeapplication executing on a client device 225. When accessing informationresources, the client device 225 can execute instructions (e.g.,embedded in the native applications, in the information resources, etc.)that cause the client devices 225 to display capture interfaces, such asthe capture interfaces described herein below in conjunction with FIGS.3A-3B. The client device 225 (or the broadcast receiver devices 220) canpresent different types of content, such as notifications, Internet ornetworked live streams of live events (e.g., which may correspond tobroadcasts of live events received by the broadcast receiver device 220)or other types of interactive content described herein. In general,content can include any type of media (e.g., images, video, animations,graphics, audio, etc.) that can be presented to a player via theinput/output interfaces of a client device 225, and/or broadcastreceiver device 220. Content, such as schedule recordings, can bedisplayed.

In response to interaction with user interface elements, the devices 225can transmit information, such as account information (e.g., changingaccount parameters, changing login information, etc.), interactioninformation, selections of wager amounts, selections of wagerparticipation in live events, or other signals to the event capturesystem 205. In some implementations, in response to the receivinginformation, the event capture system 205 can identifying a broadcastreceiver device 220 and generate recording instructions for theparticular broadcast receiver device to record a live event associatedwith the received information (e.g., wager).

As described herein, a client device 225 can receive one or moreinstructions with objects presented on the display of the client device225 (as shown with reference to FIG. 3A-3B). In some implementations,the objects can be interactable (e.g., actionable objects) that can betap interactions, click interactions, or other types of indications thata user is engaged with a particular user interface element. Upondetecting an interaction with a particular user interface element, theclient device 225 can execute instructions (e.g., processor-readablecode, a script, etc.) that cause the client device 225 to transmit anappropriate signal to the event capture system 205. A signal can includeany information specified by the instructions associated with theparticular actionable object with which the user interacted. The signalscan include, for example, a wager, a request to stop recording a liveevent associated with an ongoing wager, a request to delete a recordingof a live event associated with a previous wager, among others.

As described herein, a client device 225 and the event capture system205 can exchange messages containing information that causes a recordingto be schedule for one or more live events. In some implementations, therecording instructions can be transmitted in real-time upon receiving awager from a player. In various implementations, recording instructionscan transmitted at set intervals (e.g., every minute, every hour, everyday at noon, etc.). In some implementations, the recording instructionsmay be packaged together such that one or more recordings can bescheduled by the client device 225 in response to receiving therecording instructions from the event capture system 205.

The database 250 can be a computer-readable memory that can store ormaintain any of the information described herein. The database 250 canmaintain one or more data structures, which may contain, index, orotherwise store each of the values, pluralities, sets, variables,vectors, numbers, or thresholds described herein. The database 250 canbe accessed using one or more memory addresses, index values, oridentifiers of any item, structure, or region maintained in the database250. The database 250 can be accessed by the components of the eventcapture system 205, or any other computing device described herein, viathe network 210. In some implementations, the database 250 can beinternal to the event capture system 205. In some implementations, thedatabase 250 can exist external to the event capture system 205 and maybe accessed via the network 210. The database 250 can be distributedacross many different computer systems or storage elements and may beaccessed via the network 210 or a suitable computer bus interface. Theevent capture system 205 can store, in one or more regions of the memoryof the event capture system 205, or in the database 250, the results ofany or all computations, determinations, selections, identifications,generations, constructions, or calculations in one or more datastructures indexed or identified with appropriate values. Any or allvalues stored in the database 250 may be accessed by any computingdevice described herein, such as the event capture system 205, toperform any of the functionalities or functions described herein. Insome implementations, the database 250 can be similar to or include thestorage 128 described herein above in conjunction with FIG. 1C. In someimplementations, instead of being internal to the event capture system205, the database 250 can form a part of the cloud computing system ofFIG. 1B. In such implementations, the database 250 can be a distributedstorage medium in a cloud computing system and can be accessed by any ofthe components of the event capture system 205, by the broadcastprovider system 215, the broadcaster receiver devices 220 (e.g., via theplayer interface similar to that depicted in FIGS. 3A-3B, etc.), or theclient devices 225, or any other computing devices described herein.

The database 250 can store one or more accounts 255 (sometime referredto herein as “player profiles”) associated with a player of a broadcastreceiver device 220 and/or a client device 225. The account 255 can be aplayer profile that includes information about a player and informationabout one or more broadcast receiver devices 220 and/or one or more ofthe client devices 225 used to access the event capture system 205 usingthe account 255. For example, identifiers of an account can be used toaccess the functionality of the event capture system 205. Theidentifiers can include a username, a password, an e-mail address, aphone number, a personal identification number (PIN), a secretcode-word, device identifiers for use in a two-factor authenticationtechnique, among others. The account 255 can store information aboutwagers (e.g., historical, ongoing, etc.), events, and notifications thatare provided by the live system 205. The account 255 can store a creditbalance, wager information (e.g., an amount of a wager, a timestampassociated with a wager, information about broadcast receiver devices220 including historical device data associated with previously viewedevents, a client device identifier of a client device 225 or a broadcastreceiver device 220 that was used to place the wager, a broadcastreceiver device identifier of a device that was used to place the wageror presented a notification, a broadcast provider system 215 identifierthat provides one or more services to the account, etc.). The account255 can store information about a client device 225 or a broadcastreceiver device 220 used to access the event capture system 205 such asan IP address, a MAC address, a GUID, an account name (e.g., the name ofa user of the client device 225, etc.), device name, among others. Theaccount 255 may include one or more broadcast receiver devices 220 usedby the player. In some implementations, an account 255 can be created bythe event capture system 205 in response to an account creation requesttransmitted by a client device 225. The account creation request caninclude any of the account information described herein.

The database 250 can store or maintain play information 260 associatedwith each of the one or more accounts 255. The play information 260 caninclude event information for event previously viewed and/or wagered, orcurrently viewing and/or wagering, by a client device 225 and/orbroadcast receiver device 220 having a corresponding account 255. Insome implementations, a client device 225 accessing the event capturesystem 205 may not be associated with an account 255. In suchimplementations, the event capture system 205 can automatically createan account 255 using an identifier of the client device 225 provided bythe client device 225 and/or an identifier of the broadcast receiverdevice 220 provided by the broadcast provider system 215 and/orbroadcast receiver device 220. The play information 260 can includeinformation about previous wagers, actions, interactions, or other dataprovided by the devices described herein (e.g., 215, 220, 225) duringthe interaction with an event (e.g., viewing, wagering, selecting, etc.)provided by the event capture system 205. The play information 260 canmaintain an event state of one or more event (e.g., before the event,during the event, and after the event). As described herein, the eventstate can include one or more data structures that include anyinformation related to an event state, such as current time remaining,timeouts left, wager information, stoppages, injuries, information aboutwhether the user has indicated a desire to participate in wageropportunities (e.g., select a notification while viewing a differentevent), event statistics, or other event state data described herein. Insome implementations, the indications of the event state can be receivedas an event as the game occurs (e.g., as the event is processed by theevent capture system 205 according to the capture instructions 265,etc.). The event state can include options that a user may take at eachportion of an event, and any actions (e.g., interactions,pausing/waiting for a particular duration at stored timestamps, etc.)the broadcast receiver device 220 and/or client device 225 takes inresponse to said options.

The database 250 can store or maintain capture instructions 265. As usedherein, an “event” may be any occurrence of a live event broadcast suchas, but not limited to, a competition or game. In some embodiments, eachcompetition and/or game may have one or more events during play (e.g.,entirety of game, first quarter, second period, any time period, amongothers). For example, a football game may have a first event that is theentire game, a second event that is the second quarter, and a thirdevent that is the time period between the last two minutes of the fourthquarter. The capture instructions 265 can include instructions to recordcontent of events described herein (e.g., recording instructions). Thecapture instructions 265 can include one or more notification that areprovided in response to a wager received. In short, the captureinstructions 265 can include instructions to capture live event contentfrom start to finish (or for a particular time period) and schedulingrecords on broadcast receiver devices 220 directly (e.g., via network210) and/or indirectly (e.g., via broadcast provider system 215). Thecapture instructions 265 can be stored in one or more data structuresthat are indexed by an event name (e.g., Packers v. Bears, Jets v.Giants, Knicks v. 76ers, Yankees v. Astros, any other event, etc.), bywager identifier (e.g., wager 459393430, wager 459393431, wager459393432, etc.), or by broadcast receiver device identifier (e.g.,JK7BN, IU5FB, MC0VA, etc.). The capture instructions 265 can beprocessor executable instructions that cause the event capture system205 to provide one or more instructions and/or content (such asnotifications and schedules) to a broadcast receiver device 220, via acommunication session. In some implementations, the capture instructions265 can include artificial intelligence models (e.g., machine learningmodels, neural network, decision trees, ruled-based lookup table, etc.)that cause the event capture system 205 to provide recordinginstructions for events associated with one or more wagers.

The capture instructions 265 can include odds information, which can bestored as probability values of certain in-game events occurring. Theodds information can be altered based on actions taken by the player.The odds information can reflect a particular expected outcome (e.g., anexpected value of player loss, an expected value of player win, etc.).The event capture system 205 can use the capture instructions 265 toupdate the event state in the play information 260 by monitoring a liveevent as the live event is played, viewed, and/or recorded by thebroadcast receiver device 220. In various implementations, viewershipand number of recordings can be determined based on receiving statisticdata from the broadcast provider system 215 indicating the number ofbroadcast receiver devices 220 viewing and/or recording one or moreparticular events. In some implementations, the capture instructions 265can update the odds information in response to an indication of a wager.The capture instructions 265 can include descriptions of events or eventcriteria that can activate (e.g., provide, etc.) recording instructions.For example, during a football game, the event capture system 205 candetect a wager, and determine to provide a recording instructions toeach of the broadcast receiver devices 220 associated with the accountof the player that wagered, that can cause the broadcast receiverdevices 220 to initiate a recording of a broadcast of the live event. Inanother example, during a basketball game, the event capture system 205can detect one or more wagers, and determine to provide recordinginstructions to each of the broadcast receiver devices 220 associatedwith each account of the players that wagered, that can cause eachbroadcast receiver device 220 to initiate a recording of a broadcast ofthe live event. The recording instructions can specify the conditionsunder which the recording should occur and/or if any alerts should beprovided to the player. Each of the components of the event capturesystem 205 can access, update, or modify the accounts 255, the playinformation 260, or the capture instructions 265, to carry outfunctionalities described herein. In various implementations, thecapture instructions 265 can include API calls for communicating withthe broadcast provider system 215, API calls for communicating with thebroadcast provider devices 220, and API calls for executing anapplication on the broadcast provider devices 220 that can causerecordings to be scheduled. In some implementations, the broadcastreceiver devices 220 can maintain some or all of the captureinstructions 265, which may correspond to or include API function callsfor DVRs, cable boxes, set top boxes, or satellite boxes.

Referring now to the operations of the event capture system 205, thewager analyzer 230 can access and identify wagers related to a liveevent. The one or more wagers can be provided by the broadcast receiverdevices 220 or the client devices 225, and may include an identifier ofa live event, a message type, or information related to a condition ormoment that occurred or could occur in the live event. In someimplementations, wagers can be transmitted by the broadcast providersystem 215 215 (e.g., where the broadcast receiver devices 220communicate with the event capture system 205 via the broadcast providersystem 215), the broadcast receiver devices 220 directly (e.g., via thenetwork 210), and/or the client devices 225, and can include one or morewagers associated with a live event broadcast.

In some implementations, one or more of the wagers can include anidentifier of a live event broadcast. Each wager can indicate acorresponding broadcast receiver device 220 from which the wager wastransmitted that is receiving the live event broadcast from thebroadcast provider system 215 (or directly from event capture system205) and can include event information of a live event broadcast. Insome implementations, the wagers can be identified from communicationstransmitted by one or more of the client devices 225. In particular,wagers for events can be made on an application of the client devices225 and can be transmitted to the live event system 205 for analysis. Inresponse to receiving the wager, the live event system 205 canautomatically generate recording instructions for the event and transmitthe instructions (e.g., which may include API calls, or otherinstructions as described herein) to the broadcast receiver device 220(e.g., which may be an application executing on a smart television,etc.)

In various implementations, the wager analyzer 230 can access themessages via one or more content sources (e.g., broadcast providersystem 215). Upon receiving and/or accessing the messages, the receiveranalyzer 235 can determine to identify at least one broadcast receiverdevice 220 associated with the player that made a wager. In particular,one or more broadcast receiver devices 220 may be registered with theplayer and can be stored in accounts 255 and can include deviceidentifiers and communication information (e.g., IP address, MACaddress, service provider information, etc.) related to the broadcastreceiver devices 220, such that when a wager is identified by the wageranalyzer 230, the received analyzer can identify a broadcast receiverdevice 220 associated with the player that made the identified wager.

In various implementations, the receiver analyzer 235 can identify oneor a subset of broadcast receiver devices 220 to provide instructions torecord the live event associated with the identified wager. That is, thereceiver analyzer 235 can identify the broadcast receiver device 220based on account 255 and play information of the live event stored indatabase 250. Additionally, the identified broadcast receiver device 220can be identified based on one or more attributes of each player profileof the plurality of player profiles stored in accounts 255.

In some implementations, the instruction generator 240 can generaterecording instructions for the broadcast receiver device 220 based onidentifying the broadcast receiver device 220 from a wager. satisfyingthe notification transmission policy. The recording instructions caninclude, for example, API instructions to communicate with anapplication of the broadcast receiver device 220 to cause a recording tobe scheduled (e.g., via a DVR, cable box, set top box, satellite box,etc.). In some implementations, the instructions can include actionableand information objects for display on the broadcast receiver device 220informing the user of a scheduled recording and/or ongoing recording. Inimplementations where the broadcast receiver devices 220 are cableboxes, set top boxes, or satellite boxes, and as described herein above,the broadcast receiver devices 220 can receive recording instructionsfrom a broadcast provider system 215, for example, via a proprietarybroadcast network. In conventional broadcast systems, broadcast receiverdevices 220 cannot automatically schedule recordings based on a wager orother indication made by the player. The system 200 is an improvementover these conventional systems because the event capture system 205 cangenerate instructions that cause an application executing on thebroadcast receiver device 220 to automatically schedule a recording ofan identified live event (or portion thereof).

The instructions generated by the instruction generator 240 andtransmitted by the capture communicator 245 can be received, forexample, by the broadcast provider system 215, and can includeindications or identifiers of the broadcast receiver devices 220 towhich the recording instructions are directed. The recordinginstructions can include one or more API calls for scheduling arecording. In some implementations, the instructions can includeinstructions to display notifications at the broadcast receiver devicewith live content, and can include one or more scripts that cause theactionable and information objects to be actionable, as describedherein. In some implementations, the instruction generator 240 cangenerate the instructions based on a determined type of broadcastreceiver device 220 (e.g., broadcast receiver device X can use API callsX to schedule a recording, broadcast receiver device Y can use API callsY to schedule a recording, broadcast receiver device Z can use API callsZ to schedule a recording, etc.). For example, a cable box may require adifferent type of instructions than a set top box, or a cable box thatreceives a satellite signal via a satellite dish. To accommodate fordifferent types of broadcast receiver devices 220, the instructiongenerator 240 can maintain sets of templates for each type of broadcastreceiver device 220. Similarly, the broadcast receiver device 220 (e.g.,if the broadcast receiver device 220 is a smart television) may maintainor store API calls for a variety of DVRs, cable boxes, set top boxes, orsatellite boxes.

Once generated, the capture communicator 245 can transmit the recordinginstructions to the broadcast receiver device 220, causing the broadcastreceiver device 220 to schedule a recording, as described herein. Insome implementations, the capture communicator 245 can transmit therecording instructions to the broadcast provider system 215. Theinstructions can include, for example, indications of the one or morebroadcast receiver devices 220 that are to receive the recordinginstructions. Upon receiving the recording instructions from the capturecommunicator 245, the broadcast provider system 215 can identify the oneor more broadcast receiver devices 220 (e.g., destinations) as indicatedin the instructions, and transmit the recording instructions to each ofthe destination broadcast receiver devices 220. The applicationexecuting on the broadcast receiver device 220 can receive the recordinginstructions and use one or more API calls to schedule a recording. Itshould be understood that any other functionality as described hereincan be carried out by the broadcast receiver device 220 via theapplication or the recording instructions. Similarly, if an applicationexecuting on the broadcast receiver device 220 (e.g., which may be asmart television), receives the recording instructions, the applicationcan identify a corresponding DVR, cable box, set top box, or satellitebox in communication with the broadcast receiver device 220, andschedule a recording in accordance with the instructions at the DVR,cable box, set top box, or satellite box, as described herein.

In some implementations, the capture communicator 245 can provide thebroadcast receiver devices 220 (e.g., via the broadcast provider system215) instructions to schedule and record live events with notificationinstructions, which cause the broadcast receiver device 220 to display anotification of a recording associated with the identified wager. Insome implementations, the instructions can be directed to the broadcastprovider system 215, which can send corresponding signals to identifiedbroadcast receiver devices 220 to schedule a recording for a broadcastidentified in the instructions (e.g., via one or more APIs, etc.). Theevent capture system 205, via the capture communicator 245, canestablish a communication session with the broadcast receiver device 220to provide (or transmit) the recording instructions.

Referring briefly now to FIG. 3A, depicted is an example live eventbroadcast 300A displayed on a broadcast receiver device, such as thebroadcast receiver device 220, the client device 225, or anothercomputing device described herein. The live event broadcast 300A caninclude a display device 302 that includes a live event window 328 and anotification window 304. The display device 302 may be a broadcastreceiver device 220 and/or client device 225. In some implementations,the notification window 304 may be presented and the live event window328 may be adjusted (e.g., automatically re-dimensioned to fit thenotification window 304) based on receiving recording instructions todisplay a notification identifying one or more live events scheduled forrecording. In various implementations, the recording instructions may bereceived from the broadcast provider system 215 (e.g., via a cabledistribution network or network 210) and/or from event capture system205 (e.g., via network 210).

As shown in the FIG. 3A, the live event broadcast 300A can includeactionable objects (e.g., 308, 310) that can be interacted with (e.g.,selected, clicked) depicting scheduled recording. The player caninteract with one or more of the recording actionable objects to viewthe recording schedule and the one or more wagers associated with thescheduled recording. For example, a player may select actionable object308 to review the scheduled recording of the Packers/Bears live. Inanother example, a player may select actionable object 310 to adjust(e.g., increase, decrease) a wager amount prior to the scheduledrecording. In some implementations, it should be understood that thepresented notifications (e.g., FIG. 3A-3B) may be for one or more liveevents and the depictions of the notification window 304 in the liveevent broadcast 300A are purely example notifications, and otherconfigurations including other content, such as notifications for one ormore recordings with corresponding wagers are possible. Furthermore, invarious implementations, it should be understood that a wager may be anyasset of value such as, but not limited to, fiat currency, digitalcurrency, cryptocurrency, credits (e.g., distributed by event capturesystem 205), coupons, among others.

Additionally, the live event broadcast 300A can include informationobjects (e.g., 306) that can be configured to provide content viadisplay device 302. It should be understood that the labels, elements,objects, locations, and depictions of the live event broadcast 300A arepurely example interface elements, and other configurations includingother content, such as depictions of live events (e.g., football,basketball, baseball, soccer, wrestling, fighting, online gaming) arepossible. An interaction with the actionable objects can cause thebroadcast receiver device 220 and/or client device 225 to transmit theindication and/or selection to the event capture system 205, asdescribed herein.

Referring back now to FIG. 2 , the wager analyzer 230 can access one ormore messages that can include, but are not limited to, one or morewagers associated with one or more live events. The wager analyzer 230can utilize one or more application programming interfaces (API) toaccess wagers from the broadcast receiver devices 220, the clientdevices 225, and/or broadcast provider system 215. For example, variousdevices such as broadcast receiver devices 220 and client devices 225can execute an application to make a wager. The wager may be stored onthe various devices and the wager analyzer 230 may periodically (or inreal-time) access the storage of the various devices (e.g., 220, 225) todetermine if a wager occurred. Accessing storage can include queryingone or more data storages. In particular, the facilitation ofcommunication can be implemented as an application programming interface(API) (e.g., REST API, Web API, customized API), batch files, SDK,and/or queries. In various implementations, the event capture system 205can also be configured to control access to resources of the eventcapture system 205 and database 250. In some implementations, the wageranalyzer 230 can generate identifiers for wagers such that each wagercan be unique. In various implementations, as players make wagers, theevent capture system 205 can receive an identifier associated with thewager and data associated with the wager (e.g., wager amount, wagertype, live event, broadcast or event schedule, etc.).

One or more APIs can be used by the event capture system 205 (e.g., inparticular, the wager analyzer 230) and/or computing systems to exchangedata and make function calls in a structured format. The API may beconfigured to specify an appropriate communication protocol using asuitable electronic data interchange (EDI) standard or technology. TheEDI standard (e.g., messaging standard and/or supporting technology) mayinclude any of a SQL data set, a protocol buffer message stream, aninstantiated class implemented in a suitable object-oriented programminglanguage, an XML file, a text file, an Excel file, a web service messagein a suitable web service message format (e.g., representational statetransfer (REST), simple object access protocol (SOAP), web servicedefinition language (WSDL), JavaScript object notation (JSON), XMLremote procedure call (XML RPC). As such, EDI messages may beimplemented in any of the above or using another suitable technology. Insome implementations, the communication session (e.g., via an API) canbe established between the live event system 205 and broadcast providersystem 215 and periodically (or in real-time) the data received from thebroadcast receiver devices 220 can be batched and sent to the live eventsystem 205 using an EDI messages.

In some implementations, the receiver analyzer 235 can access accounts255 and/or wagers (e.g., from wager analyzer 230) that can include, butare not limited to, one or more broadcast receiver device identifiersassociated with one or more client devices 225 (e.g., client deviceidentifiers) and/or broadcast provider system 215 (e.g., client deviceidentifiers). The receiver analyzer 235 can utilize one or moreapplication programming interfaces (API) to access identifiers andcommunication information (e.g., IP address, geographic locationinformation, broadcast provider service, network protocol, etc.) fromthe broadcast receiver devices 220, broadcast provider system 215,client devices 225, and accounts 255 in database 250. In particular, thefacilitation of communication can be implemented as an applicationprogramming interface (API) (e.g., REST API, Web API, customized API),batch files, SDK, and/or queries. In various implementations, eachclient device 225, broadcast receiver device 220, wager, and live eventcan have a unique identifier. For example, each client device 225 mayhave a unique identifier that follows the following format, CD-XXXXX,where the X's are randomly generated by the event capture system 205(e.g., CD-45GB6, CD-9838H, etc.). However, it should be understood thatthis example is non-limiting and that other unique identifiers for theclient devices 225 are possible (e.g., MAC address, GUID, etc.). Inanother example, each broadcast receiver device 215 may have a uniqueidentifier that follows the following format, BRD-XXXXXXX, where the X'sare randomly generated by the event capture system 205 (e.g.,BRD-76NX81B, BRD-MKFIZB5, etc.). However, it should be understood thatthis example is non-limiting and that other unique identifiers for thebroadcast receiver devices 220 are possible (e.g., MAC address, GUID,etc.). It should be understood that each identifier can follow anyformat that can uniquely identify each device, wager, and/or live event.

The instruction generator 240 can generate recording instructions thatcan include API calls for communicating with an application on thebroadcast receiver device 220 that can execute instructions to schedulea recording. In some implementations, the recording instructions may beunique to the type of broadcast receiver device 220. Additionally, theinstruction generator 240 can utilize a broadcast schedule of live eventto determine the instructions for transmitting. In particular, thebroadcast schedule can be received form the broadcast provider system215, broadcast receiver device 220, and/or a client device 225. Invarious implementations, when recording instructions are generated, thecapture communicator 245 may communicate with the identified broadcastreceiver device 220 of the identified wager. The communication may be inthe form of a client message including recording data to configure thebroadcast receiver device 220 to capture and store recording of a liveevent. The captured recording can be stored as recording data in thecapture instructions 265 and/or in accounts 255. In someimplementations, the recording instruction can cause the display of thebroadcast receiver device 220 and/or client device 225 to display anotification indicating a recording has been set.

In various implementations, the player can configure when recordinginstructions can be generated by instruction generator 240 andtransmitted by capture communicator 245. For example, based on the typeof wager (e.g., parlay, above $50, money line) or client message (e.g.,entire games, less than 10-minute recording, designated teams), theinstruction generator 240 can generate instructions if the type of wageror message satisfies a player's configuration. The configurations can bestored in accounts 255 and queried by the instruction generator 240. Therecording instructions 265 can include one or more checks such as, butnot limited to, prompting the instruction generator 240 to query theconfiguration stored in accounts 255 prior to generating recordinginstructions for a broadcast receiver device 220. In someimplementations, the player can update configuration in real-time. Insome implementations, the player configuration may indicate that norecordings should be scheduled for the player's wagers.

In some implementations, the recording instructions generated by theinstruction generator 240 are for recording a critical moment (e.g.,wager on a particular player, wager on a particular team to win, wageron a particular event) or period of time corresponding to the wager. Forexample, if the player wagers on the 4th quarter of a football game, therecording instructions will schedule a recording for only the 4thquarter. In another example, if the wager is on a team to win, therecording instruction will schedule a recording for the final fewmoments of the game (e.g., last minute, last 5 seconds, etc.).Additionally, the player can configure in their player profile (oraccount settings) what period of time they would like recordedassociated with a wager. For example, the user may configure recordingof moments to be 15 seconds before and after the moment. In anotherexample, the user may configure recordings of the end of game to startwhen there is 30 second left. In some implementations, the attributes ofthe recording (e.g., what portion of the live event to record, whetherto record the live event, etc.) can be specified on a per-wager basis(e.g., with each wager, etc.).

Referring now to FIG. 3B, depicted is an example live event broadcast300B displayed on a broadcast receiver device, such as the broadcastreceiver device 220, the client device 225, or another computing devicedescribed herein. The live event broadcast 300B can include similarfeatures and functionalities of FIG. 3A. The live event broadcast 300Bcan include a display device 302 that includes a live event window 328.The display device 302 may be a broadcast receiver device 220 and/orclient device 225. In some implementations, a notification may bepresented (or overlayed) within live event window 328 based on receivingrecording instructions to schedule a recording of a live event. Invarious implementations, the notification may be for a live eventcurrently recording. Alternatively, the notification may be for a liveevent scheduled to be recorded. The instructions to present thenotification and one or more actionable objects can be received from thebroadcast provider system 215 (e.g., via a cable distribution network ornetwork 210) and/or from event capture system 205 (e.g., via network210).

As shown in the FIG. 3B, the live event broadcast 300B can includeactionable objects (e.g., 312) that can be interacted with (e.g.,selected, clicked) depicting a recording notification. The player caninteract with one or more of the actionable objects to view wagers andthe recording schedule. For example, a player may select actionableobject 312 to view the current one or more wagers on the Mets/Yankeeslive event. Additionally, it should be understood that the labels,elements, objects, locations, and depictions of the live event broadcast300B are purely example interface elements, and other configurationsincluding other content, such as depictions of live events (e.g.,football, basketball, baseball, soccer, wrestling, fighting, onlinegaming) are possible. An interaction with the actionable objects cancause the broadcast receiver device 220 and/or client device 225 totransmit the indication and/or selection of one or more wagers to theevent capture system 205, as described herein. After which, a creditbalance can be deducted.

Referring back to FIG. 2 , in various implementations described herein,content can be provided to the broadcast receiver devices 220 by theevent capture system 205 or broadcast provider system 215 in one or morefeeds of content. The feeds of content may include content items thatindicate updated start times of live events, content items that indicateinformation relating to wagers placed on the live events, content itemsrelating to wagers placed on the live event (e.g., wagers that identifya player profile associated with the broadcast receiver device, otherwagers placed on the live event, etc.), and content items that indicatedetected conditions of live events (e.g., changes in score, points,plays that occur during the live events, etc.), among others.

The event capture system 205 can detect the outcomes of wagers bymonitoring the conditions of the live events identified by the wagers.Detecting the outcomes of wagers can including retrieving or monitoringan external repository that maintains a record of occurrences in thelive events or a record of the state of a live event that indicatesvarious conditions of the live events on which wagers can be placed.Detecting the outcomes of wagers can include polling one or more remotecomputing devices, which may be operated by persons that are present ata live event. In some implementations, user input can be provided at theremote computing devices to indicate an update to a state of the liveevent, or to indicate an outcome of one or more wager conditions. Theindications can be recorded by the remote computing device, which cantransmit with the indications to the event capture system 205. Based onthe indications, the event capture system 205 can determine whether oneor more wagers have been closed by evaluating the conditions in eachwager against the updated state provided by the remote computing device.In implementations where the remote computing devices themselvesindicate an outcome of a wager, the event capture system 205 can detectthe outcome of wagers by parsing the indications. In someimplementations, the event capture system 205 can detect outcomes wagersbased on the changes in the state (e.g., in-game time, score, one ormore plays, or status of a live sporting event, etc.) of the live event.

The event capture system 205 can update the status of the wagers basedon the detected outcomes by recording the outcomes of the wagers in thedatabase. Upon detecting an outcome of a wager, the event capture system205 can generate a content item that includes an indication of the wageroutcome, and can display the content item on a broadcast receiver device220 with a broadcast of a live event, as described herein. In someimplementations, the content item can include instructions that causethe broadcast receiver device to navigate to the live event on which thewager was placed (e.g., change the channel being displayed). Theoutcomes of wagers may also be utilized in connection with the varioustechniques described herein.

The event capture system 205 may receive or update permissions todisplay one or more content items (e.g., in the user interfaces shown inFIGS. 3A-3C) with live content. For example, the broadcast receiverdevices 220 can perform an opt-in process to authorize the display ofone or more content items with broadcasts of live events. The opt-inprocess may include providing a code, which a user of the broadcastreceiver device 220 can scan using a second device (e.g., a smartphone,a tablet computer, etc.). Scanning the code can cause the second deviceto navigate (e.g., via a web-browser or native application deep-link) toa URL embedded in the scanned code. The code including the URL can begenerated in response to a corresponding interaction with a button oruser interface element presented by the application executing on thebroadcast receiver device 220, to initiate the opt-in process. The URLcan cause the second device to navigate to a landing page (e.g., a userinterface) provided by the event capture system 205 that acceptsauthentication credentials corresponding to a player profile. Once theauthentication credentials have been entered, the event capture system205 can verify the authentication credentials, and provide a second page(e.g., a user interface) that enables the user to modify permissions forpresenting content with live events on the broadcast receiver device 220that presented the code. In some implementations, one or more of thelanding page that accepts authentication credentials and the second pagethat enables the user to modify the permissions can be navigated to anddisplayed on the broadcast receiver device 220.

The second page that enables the user to modify permissions forpresenting content with live events on the broadcast receiver device 220that presented the code can include one or more selectable userinterface elements that enables selection of whether content can bedisplayed in connection with live broadcasts on the broadcast receiverdevice. The selectable user interface elements can enable or disable thedisplay of certain types of content items (e.g., wagers, messages fromother players, etc.). The selectable user interface elements can be usedto specify time period restrictions during which content items are notdisplayed on the broadcast receiver device 220 with live content. Theselectable user interface elements can be used to specify time periodrestrictions during which content items are not displayed on thebroadcast receiver device 220 with live content. The updates to thepermissions can be stored in association with an identifier of thebroadcast receiver device 220, and can form a part of one or moreselection policies to select content for the broadcast receiver device220.

Content items, such as the content items (sometimes referred to asalerts or notifications) shown in FIGS. 3A-3C, can be displayed by anapplication that executes on the broadcast receiver device 220. Asdescribed herein, the broadcast receiver device 220 can include memorythat can store processor-executable instructions. Theprocessor-executable instructions can include the application. To launchthe application, a player can access a menu provided by an operatingsystem or other low-level software of the broadcast receiver device 220.The menu can include an interactive user interface element that launchesthe application, or causes the application to present a visible userinterface (e.g., one or more of the interfaces described in connectionwith FIGS. 3A-3C, etc.). Various additional user interface elements canbe displayed by the application that enable navigation between differentviews, windows, content items, or user interfaces of the application.

As described herein, one or more of the content items provided to anddisplayed by the broadcast receiver device 220 with live content can beinteractive content items. The interactive content items can includebuttons, hyperlinks, graphics, or other types of interactive userinterface elements that cause the broadcast receiver device 220 toperform one or more operations. For example, the content item caninclude (e.g., in metadata of the content item) processor-executableinstructions, interpretable scripts or code, or an identifier of anoperation to perform. Upon an interaction with the content item, thebroadcast receiver device 220 can perform the various operationsspecified by the metadata of the content item. Example operationsincluding navigating to a live broadcast indicated in the content item,placing a wager on a live event, modifying player profile attributes,request additional or alternative content to display with a current oralternative broadcast, or other operations described herein. In anexample embodiment, upon an interaction with a content item that causesthe broadcast receiver device 220 to navigate to a live broadcast, thebroadcast receiver device 220 can transmit a request for content itemsto the event capture system 205, which can provide corresponding contentitems for display with the live broadcast in response to the request. Inanother embodiment, the broadcast receiver device 220 can navigate tothe live broadcast indicated in the content item without requestingcontent items for display.

Referring now to FIG. 4 , depicted is an illustrative flow diagram of amethod 400 for controlling computer recorded data based on clientmessages. The method 400 can be executed, performed, or otherwisecarried out by the event capture system 205, the computer system 100described herein in conjunction with FIGS. 1A-1D, or any other computingdevices described herein. In brief overview of the method 400, the eventcapture system (e.g., the event capture system 205, etc.) can identify awager (STEP 402), identify a broadcast receiver device (STEP 404),generate recording instructions (STEP 406), and transmit instructions(STEP 408).

In further detail of the method 400, the event capture system (e.g., theevent capture system 205, etc.) can identify a wager corresponding to alive event associated with a client device (STEP 402). A wager caninclude, but is not limited to, money line bets, straight bets,proposition (or prop) bets, teaser bets, among others. In someimplementation, the wager can be identified after receiving a request torecord live events corresponding to wagers associated with the clientdevice. The request can include one or more wagers associated with oneor more live events. In some implementations, the request may includedevice identifiers and/or account information identifying the origin ofthe messages (e.g., client devices 225, broadcast receiver devices 220).Additionally, the requests may include live event information such as,statistics of the live event. In some implementations, a wager maycorrespond to a portion of the live event. For example, the player maywager on the fourth quarter of a football game, or the second half of asoccer game. In the following examples, the wager identified may beassociated with a game play time period (e.g., stored in playinformation 260), such that when the recording instructions aregenerated in STEP 406, the recording instructions may initiate arecording of only the portion of the live event corresponding to thewager.

The event capture system can identify a broadcast receiver devicecorresponding to the client device (STEP 404). In some implementations,the event capture system can maintain a data structure storing anassociation between an identifier of the wager, an identifier of theclient device, and an identifier of the broadcast receiver devicecorresponding to the client device. For example, the data structure maybe stored in a database (e.g., database 250) in the account (e.g.,accounts 255) of the player. In the following example, each wager mayhave a unique identifier (e.g., GB6YH2), a unique client deviceidentifier (e.g., 340959208560194), and a unique broadcast receiverdevice identifier (e.g., BRD-0949839). In various implementations, theplayer may have a data structure that includes an association of withmore than one wager identifier, client device identifier, and broadcastreceiver device identifier such that one wager identifier associatedwith a player may be associated with two client device identifiers andfive broadcast receiver device identifiers.

In various implementations, the event capture system can determine thatthe broadcast receiver device is authorized to record the broadcast ofthe live event. For example, the event capture system may determineequipment information (e.g., type of display, device capabilities),account information (e.g., account credentials, adults-only access, kidaccess, preferences), etc. In some implementations, the broadcastreceiver device can be identified from a user profile used by the clientdevice to communicate with the one or more processors. For example, eachuser profile may have enrolled or registered broadcast receiver devicesthat can be authorized and/or configured to capture live events.

The event capture system can generate recording instructions for thebroadcast receiver device that cause the broadcast receiver device toinitiate a recording of a broadcast of the live event (STEP 406). Insome implementations, the recording instructions can be generated inresponse to determining a broadcast schedule of the live event based oninformation received from the broadcast receiver device. Alternatively,the recording instructions can be generated in response to determining abroadcast schedule of the live event based on information received froma third-party data source (e.g., news feeds, social media, broadcastprovider system 215, internet content, among others). Accordingly, thegenerated recording instructions can be based on the broadcast scheduleof the live event. For example, after identifying a wager and broadcastreceiver device, the event capture system can request (e.g., frombroadcast provider system 215, broadcast receiver device 220,third-party data sources, etc.) or access (e.g., from play information260) one or more broadcast schedules and search the broadcast schedulesto identify the live event associated with the wager.

The event capture system can determine when a particular portion of alive event that corresponds to a wager placed by a player, as describedherein, and subsequently generate recording instructions as describedherein to record that moment at a corresponding broadcast receiverdevice. In some implementations, the event capture system may recordportions of a live event that correspond to a critical moment (e.g., acritical event), which may be identified as the last moments of aquarter in a football game, when a score is tied, or when a large influxof messages corresponding to the live event are detected. The eventprocessing system can monitor signals related to the live event (e.g.,live event content, scheduling information from one or more datasources, etc.).

In some implementations, generating the recording instructions isresponsive to a request to record live events corresponding to wagersassociated with a client device. For example, instead of the live eventcapture system identifying a wager (as described in STEP 402), therecording instructions can be automatically generated in response toreceiving a request to record a live event associated with a wager.

In various implementations, upon making a wager, a message (sometimereferred to herein as a “client message”) may be sent to the eventcapture system that includes the wager and the live event of the wager.For example, the event capture system 205 may receive an indication of awager every time the player makes a wager. In the following example, theplayer may set one or more preferences (e.g., in accounts 255) thatindicate the event capture system should record certain wagers based onvarious parameters (e.g., any wager above $50 should be recorded, anywager based on the entire game should be recorded, etc.). In someimplementations, the recording instructions for the broadcast receiverdevice can include generating a notification for display by thebroadcast receiver device that indicates the recording of the broadcastof the live event has been scheduled. Accordingly, the request to recorda live event can be included (e.g., as data) in wagers corresponding tolive event. In some implementations, the recording instructions may befor a portion of the live event corresponding to the wager.Additionally, the recording instructions may include instructions tostore the recording (e.g., recording data) on the broadcast receiverdevice 220. For example, the recording instructions could include a filelocation designation in a storage device of the broadcast receiverdevice (e.g., or cloud, or client device 225). The recorded live eventcan be stored as recorded data for playback by the player in a suitablestorage.

The event capture system can transmit recording instructions to thebroadcast receiver device to cause the broadcast receiver device toschedule a recording for the broadcast of the live event (STEP 408). Asshown in FIGS. 3A-3B, the instructions can include various stylinginformation and live event information that can cause the display device(e.g., the broadcast receiver device 220 and/or client device 225) todisplay a notification indicating an event is scheduled to be captured(or recorded). The recording instructions can be stored in a clientmessage that can include the styling information and live eventinformation as well. In some implementations, the notification caninclude actionable objects that causes a broadcast receiver devicedisplaying the notification to display a broadcast of the live event.

In various implementations, the recording instructions can cause thebroadcast receiver device 220 to execute API calls to an application ofthe broadcast receiver device 220 to schedule a recording. The recordinginstructions can include parameters for the recording including the timelength, the event, etc. Additionally, the API calls can return asuccessful or failure indicating if the recording was scheduled. Thereturn of the API calls can be transmitted to the event capture system205. In some implementations, the API calls may be unique to thebroadcast receiver device 220 such that the API calls are specific tothe hardware and application of the broadcast receiver device 220.

Implementations of the subject matter and the operations described inthis specification can be implemented in digital electronic circuitry,or in computer software embodied on a tangible medium, firmware, orhardware, including the structures disclosed in this specification andtheir structural equivalents, or in combinations of one or more of them.Implementations of the subject matter described in this specificationcan be implemented as one or more computer programs, e.g., one or morecomponents of computer program instructions, encoded on computer storagemedium for execution by, or to control the operation of, data processingapparatus. The program instructions can be encoded on anartificially-generated propagated signal, e.g., a machine-generatedelectrical, optical, or electromagnetic signal that is generated toencode information for transmission to suitable receiver apparatus forexecution by a data processing apparatus. A computer storage medium canbe, or be included in, a computer-readable storage device, acomputer-readable storage substrate, a random or serial access memoryarray or device, or a combination of one or more of them. Moreover,while a computer storage medium is not a propagated signal, a computerstorage medium can include a source or destination of computer programinstructions encoded in an artificially-generated propagated signal. Thecomputer storage medium can also be, or be included in, one or moreseparate physical components or media (e.g., multiple CDs, disks, orother storage devices).

The operations described in this specification can be implemented asoperations performed by a data processing apparatus on data stored onone or more computer-readable storage devices or received from othersources.

The terms “data processing apparatus”, “data processing system”, “clientdevice”, “computing platform”, “computing device”, or “device”encompasses all kinds of apparatus, devices, and machines for processingdata, including by way of example a programmable processor, a computer,a system on a chip, or multiple ones, or combinations, of the foregoing.The apparatus can include special purpose logic circuitry, e.g., an FPGA(field programmable gate array) or an ASIC (application-specificintegrated circuit). The apparatus can also include, in addition tohardware, code that creates an execution environment for the computerprogram in question, e.g., code that constitutes processor firmware, aprotocol stack, a database management system, an operating system, across-platform runtime environment, a virtual machine, or a combinationof one or more of them. The apparatus and execution environment canrealize various different computing model infrastructures, such as webservices, distributed computing and grid computing infrastructures.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, declarative orprocedural languages, and it can be deployed in any form, including as astand-alone program or as a module, component, subroutine, object, orother unit suitable for use in a computing environment. A computerprogram may, but need not, correspond to a file in a file system. Aprogram can be stored in a portion of a file that holds other programsor data (e.g., one or more scripts stored in a markup languagedocument), in a single file dedicated to the program in question, or inmultiple coordinated files (e.g., files that store one or more modules,sub-programs, or portions of code). A computer program can be deployedto be executed on one computer or on multiple computers that are locatedat one site or distributed across multiple sites and interconnected by acommunication network.

The processes and logic flows described in this specification can beperformed by one or more programmable processors executing one or morecomputer programs to perform actions by operating on input data andgenerating output. The processes and logic flows can also be performedby, and apparatuses can also be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application-specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read-only memory ora random access memory or both. The elements of a computer include aprocessor for performing actions in accordance with instructions and oneor more memory devices for storing instructions and data. Generally, acomputer will also include, or be operatively coupled to receive datafrom or transfer data to, or both, one or more mass storage devices forstoring data, e.g., magnetic, magneto-optical disks, or optical disks.However, a computer need not have such devices. Moreover, a computer canbe embedded in another device, e.g., a mobile telephone, a personaldigital assistant (PDA), a mobile audio or video player, a game console,a Global Positioning System (GPS) receiver, or a portable storage device(e.g., a universal serial bus (USB) flash drive), for example. Devicessuitable for storing computer program instructions and data include allforms of non-volatile memory, media and memory devices, including by wayof example semiconductor memory devices, e.g., EPROM, EEPROM, and flashmemory devices; magnetic disks, e.g., internal hard disks or removabledisks; magneto-optical disks; and CD-ROM and DVD-ROM disks. Theprocessor and the memory can be supplemented by, or incorporated in,special purpose logic circuitry.

To provide for interaction with a user, implementations of the subjectmatter described in this specification can be implemented on a computerhaving a display device, e.g., a CRT (cathode ray tube), plasma, or LCD(liquid crystal display) monitor, for displaying information to the userand a keyboard and a pointing device, e.g., a mouse or a trackball, bywhich the user can provide input to the computer. Other kinds of devicescan be used to provide for interaction with a user as well; for example,feedback provided to the user can include any form of sensory feedback,e.g., visual feedback, auditory feedback, or tactile feedback; and inputfrom the user can be received in any form, including acoustic, speech,or tactile input. In addition, a computer can interact with a user bysending documents to and receiving documents from a device that is usedby the user; for example, by sending web pages to a web browser on auser's client device in response to requests received from the webbrowser.

Implementations of the subject matter described in this specificationcan be implemented in a computing system that includes a back-endcomponent, e.g., as a data server, or that includes a middlewarecomponent, e.g., an application server, or that includes a front-endcomponent, e.g., a client computer having a graphical user interface ora Web browser through which a user can interact with an implementationof the subject matter described in this specification, or anycombination of one or more such back-end, middleware, or front-endcomponents. The components of the system can be interconnected by anyform or medium of digital data communication, e.g., a communicationnetwork. Examples of communication networks include a local area network(“LAN”) and a wide area network (“WAN”), an inter-network (e.g., theInternet), and peer-to-peer networks (e.g., ad hoc peer-to-peernetworks).

The computing system such as the event capture system 205 can includeclients and servers. For example, the event capture system 205 caninclude one or more servers in one or more data centers or server farms.A client and server are generally remote from each other and typicallyinteract through a communication network. The relationship of client andserver arises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someimplementations, a server transmits data (e.g., an HTML page) to aclient device (e.g., for purposes of displaying data to and receivinginput from a user interacting with the client device). Data generated atthe client device (e.g., a result of an interaction, computation, or anyother event or computation) can be received from the client device atthe server, and vice-versa.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as descriptions offeatures specific to particular implementations of the systems andmethods described herein. Certain features that are described in thisspecification in the context of separate implementations can also beimplemented in combination in a single implementation. Conversely,various features that are described in the context of a singleimplementation can also be implemented in multiple implementationsseparately or in any suitable subcombination. Moreover, althoughfeatures may be described above as acting in certain combinations andeven initially claimed as such, one or more features from a claimedcombination can in some cases be excised from the combination, and theclaimed combination may be directed to a subcombination or variation ofa subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In some cases, the actions recited in the claims can beperformed in a different order and still achieve desirable results. Inaddition, the processes depicted in the accompanying figures do notnecessarily require the particular order shown, or sequential order, toachieve desirable results.

In certain circumstances, multitasking and parallel processing may beadvantageous. Moreover, the separation of various system components inthe implementations described above should not be understood asrequiring such separation in all implementations, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products. For example, the event capturesystem 205 could be a single module, a logic device having one or moreprocessing modules, one or more servers, or part of a search engine.

Having now described some illustrative implementations andimplementations, it is apparent that the foregoing is illustrative andnot limiting, having been presented by way of example. In particular,although many of the examples presented herein involve specificcombinations of method acts or system elements, those acts and thoseelements may be combined in other ways to accomplish the sameobjectives. Acts, elements and features discussed only in connectionwith one implementation are not intended to be excluded from a similarrole in other implementations or implementations.

The phraseology and terminology used herein is for the purpose ofdescription and should not be regarded as limiting. The use of“including” “comprising” “having” “containing” “involving”“characterized by” “characterized in that” and variations thereofherein, is meant to encompass the items listed thereafter, equivalentsthereof, and additional items, as well as alternate implementationsconsisting of the items listed thereafter exclusively. In oneimplementation, the systems and methods described herein consist of one,each combination of more than one, or all of the described elements,acts, or components.

Any references to implementations or elements or acts of the systems andmethods herein referred to in the singular may also embraceimplementations including one or more these elements, and any referencesin plural to any implementation or element or act herein may alsoembrace implementations including only a single element. References inthe singular or plural form are not intended to limit the presentlydisclosed systems or methods, their components, acts, or elements tosingle or plural configurations. References to any act or element beingbased on any information, act or element may include implementationswhere the act or element is based at least in part on any information,act, or element.

Any implementation disclosed herein may be combined with any otherimplementation, and references to “an implementation,” “someimplementations,” “an alternate implementation,” “variousimplementation,” “one implementation” or the like are not necessarilymutually exclusive and are intended to indicate that a particularfeature, structure, or characteristic described in connection with theimplementation may be included in at least one implementation. Suchterms as used herein are not necessarily all referring to the sameimplementation. Any implementation may be combined with any otherimplementation, inclusively or exclusively, in any manner consistentwith the aspects and implementations disclosed herein.

References to “or” may be construed as inclusive so that any termsdescribed using “or” may indicate any of a single, more than one, andall of the described terms.

Where technical features in the drawings, detailed description or anyclaim are followed by reference signs, the reference signs have beenincluded for the sole purpose of increasing the intelligibility of thedrawings, detailed description, and claims. Accordingly, neither thereference signs nor their absence have any limiting effect on the scopeof any claim elements.

The systems and methods described herein may be embodied in otherspecific forms without departing from the characteristics thereof.Although the examples provided may be useful for extracting parametersfrom invoices using a cloud computing system, the systems and methodsdescribed herein may be applied to other environments. The foregoingimplementations are illustrative rather than limiting of the describedsystems and methods. The scope of the systems and methods describedherein may thus be indicated by the appended claims, rather than theforegoing description, and changes that come within the meaning andrange of equivalency of the claims are embraced therein.

What is claimed is:
 1. A method, comprising: identifying, by one or moreprocessors coupled to memory, a wager corresponding to a live eventassociated with a client device, the wager comprising a request torecord a broadcast of the live event; identifying, by the one or moreprocessors, a broadcast receiver device corresponding to the clientdevice; generating, by the one or more processors, recordinginstructions for the broadcast receiver device that cause the broadcastreceiver device to initiate a recording of the broadcast of the liveevent; and transmitting, by the one or more processors, the recordinginstructions to the broadcast receiver device to cause the broadcastreceiver device to schedule a recording for the broadcast of the liveevent.
 2. The method of claim 1, further comprising: determining, by theone or more processors, a broadcast schedule of the live event based oninformation received from the broadcast receiver device; and whereingenerating the recording instructions for the broadcast receiver deviceis further based on the broadcast schedule of the live event.
 3. Themethod of claim 1, further comprising: determining, by the one or moreprocessors, a broadcast schedule of the live event based on informationreceived from a third-party data source; and wherein generating therecording instructions for the broadcast receiver device is furtherbased on the broadcast schedule of the live event.
 4. The method ofclaim 1, further comprising maintaining, by the one or more processors,a data structure storing an association between an identifier of thewager, an identifier of the client device, and an identifier of thebroadcast receiver device corresponding to the client device.
 5. Themethod of claim 1, further comprising: determining, by the one or moreprocessors, that the wager corresponds to a portion of the live event;and generating, by the one or more processors, the recordinginstructions to initiate a recording of only the portion of the liveevent corresponding to the wager.
 6. The method of claim 1, whereinidentifying the broadcast receiver device corresponding to the clientdevice further comprises identifying, by the one or more processors,from a user profile used by the client device to communicate with theone or more processors, an identifier of the broadcast receiver devicecorresponding to the client device.
 7. The method of claim 1, whereingenerating the recording instructions for the broadcast receiver devicefurther comprises generating a notification for display by the broadcastreceiver device that indicates the recording of the broadcast of thelive event has been scheduled.
 8. The method of claim 1, furthercomprising: determining, by the one or more processors, that thebroadcast receiver device is authorized to record the broadcast of thelive event; and generating, by the one or more processors, the recordinginstructions responsive to determining that the broadcast receiverdevice is authorized to record the broadcast of the live event.
 9. Asystem, comprising: one or more processors coupled to memory, the one ormore processors configured to: identify a wager corresponding to a liveevent associated with a client device, the wager comprising a request torecord a broadcast of the live event; identify a broadcast receiverdevice corresponding to the client device; generate recordinginstructions for the broadcast receiver device that cause the broadcastreceiver device to initiate a recording of the broadcast of the liveevent; and transmit the recording instructions to the broadcast receiverdevice to cause the broadcast receiver device to schedule a recordingfor the broadcast of the live event.
 10. The system of claim 9, whereinthe one or more processors are further configured to: determine abroadcast schedule of the live event based on information received fromthe broadcast receiver device; and generate the recording instructionsfor the broadcast receiver device further based on the broadcastschedule of the live event.
 11. The system of claim 9, wherein the oneor more processors are further configured to: determine a broadcastschedule of the live event based on information received from athird-party data source; and generate the recording instructions for thebroadcast receiver device further based on the broadcast schedule of thelive event.
 12. The system of claim 9, wherein the one or moreprocessors are further configured to maintain a data structure storingan association between an identifier of the wager, an identifier of theclient device, and an identifier of the broadcast receiver devicecorresponding to the client device.
 13. The system of claim 9, whereinthe one or more processors are further configured to: determine that thewager corresponds to a portion of the live event; and generate therecording instructions to initiate a recording of only the portion ofthe live event corresponding to the wager.
 14. The system of claim 9,wherein to identify the broadcast receiver device corresponding to theclient device, the one or more processors are further configured toidentify, from a user profile used by the client device to communicatewith the one or more processors, an identifier of the broadcast receiverdevice corresponding to the client device.
 15. The system of claim 9,wherein to generate the recording instructions for the broadcastreceiver device, the one or more processors are further configured togenerate a notification for display by the broadcast receiver devicethat indicates the recording of the broadcast of the live event has beenscheduled.
 16. The system of claim 9, wherein the one or more processorsare further configured to: determine that the broadcast receiver deviceis authorized to record the broadcast of the live event; and generatethe recording instructions responsive to determining that the broadcastreceiver device is authorized to record the broadcast of the live event.